From: Phil <email@example.com> To: firstname.lastname@example.org Subject: Shebang and python packages Date: Thu, 03 Jun 2021 22:09:13 +0100 [thread overview] Message-ID: <email@example.com> (raw) Hi all, It seems to be convention not to include python itself as a propagated-input in python packages? However the default-python version is included as a native-input for the python-build-system - this means any shebangs are hardcoded to whatever the current version of python may be. Given this hardcoding, why isn't it also convention to package the version of python that has been used to patch the shebangs as part of the package? I tend to build manifests containing my python app, and python itself to run the app. Originally I thought this was necessary to decouple the app from a specific version of python, but assuming I'm right about the patching of shebangs, this seems to be misguided - as any entry points within the app will have been hardcoded to use a version of python at build time, irrespective of the python version in the manifest? Can anyone clarify best practice and reasoning behind it? Thanks, Phil.
next reply other threads:[~2021-06-03 21:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-03 21:09 Phil [this message] 2021-06-03 21:24 ` Tobias Geerinckx-Rice 2021-06-03 21:36 ` Phil 2021-06-03 22:50 ` Tobias Geerinckx-Rice 2021-06-10 10:45 ` François J. 2021-06-13 9:16 ` Reza Housseini
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Shebang and python packages' \ /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
all messages for Guix-related lists mirrored at yhetil.org This inbox may be cloned and mirrored by anyone: git clone --mirror https://yhetil.org/guix Example config snippet for mirrors. AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git