[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#73816: python-django's manage.py tries to use a hard-coded python ex
From: |
Simon Tournier |
Subject: |
bug#73816: python-django's manage.py tries to use a hard-coded python executable |
Date: |
Tue, 10 Dec 2024 16:59:27 +0100 |
Hi,
On Tue, 15 Oct 2024 at 11:48, Gabriel Wicki <gabriel@erlikon.ch> wrote:
> The python-django package makes the admin utility create a manage.py
> file with a hard-coded python interpreter.
>
> $ guix shell python python-django -- django-admin startproject foobar
> $ head -n 1 foobar/manage.py
>
> #!/gnu/store/my2j5bzapayk59971z2ryzlajdz569f9-python-toolchain-3.10.7/bin/python
>
> I think this is wrong. The interpreter line should be
>
> #!/usr/bin/env python3
Well, I don’t know if there is a rationale for this choice. Somehow, my
understanding is: 1. python-django is byte-compiled using one specific
Python interpreter and 2. what is the guarantee that the whole code
byte-compiled with different Python interpreter will run?
Hence, that version of the specific Python interpreter is encoded.
Now, if the purpose of ’django-admin startproject foobar’ is to only
create generic configuration that does not depends on any Django or
Python version, then maybe it could be considered as wrong. :-)
Else I don’t know. I remember having a similar discussion about a
similar Python tool but I am not able to find it back.
Cheers,
simon
- bug#73816: python-django's manage.py tries to use a hard-coded python executable,
Simon Tournier <=