unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: guix-devel@gnu.org
Subject: "Sales Pitch" for Guix as Yet Another Python Package Manager
Date: Fri, 13 Jan 2023 23:20:12 +0000	[thread overview]
Message-ID: <6838deeeebf3825949022dfa8aef05dd@dismail.de> (raw)

Hi Guixers,

I'd like to get your opinions/brainstorms on the unique features that you think make Guix an excellent Python package manager over all the others: pip, poetry, pyenv, pipenv, conda, etc.

Here are two reasons I can think of:

1. You never get opaque mystery wheels🛞 but always get the Python libraries built from source including any C/C++ related dependencies. In other words, you can ensure that the entire "transitive story" can be told and accounted for down to the primordial berry.

2. Guix makes it easy to have a multi-language environment/project without having to worry about scrambling to get your non-Python deps with various build tools/package managers. 

3. You want some C, ruby, C++, etc. development dependencies in your Python project? You got it and from one CLI.

What else makes Guix unique for Python development besides the above 3 points?

The one thing I can say that we are currently missing that pyenv provides is getting any version of CPython 3 that is currently supported. Guix only conveniently provides Python 3.9. By convenient, I mean easily available from master with substitutes available. This is mostly my fault as I haven't spent the time to package the other CPython versions yet.


             reply	other threads:[~2023-01-13 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 23:20 jgart [this message]
2023-01-14  2:28 ` "Sales Pitch" for Guix as Yet Another Python Package Manager jgart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6838deeeebf3825949022dfa8aef05dd@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).