Hi folks,
I'm here again trying to up to date the django-firebird backend.
The last stable version was for django 1.8 LTS, that came to end of life,
so I want to update to 1.11 LTS first and then to 2.0.
Having said that, one of unresolved things is about adding a non-nullable
field to a popu
I personally just edit my manage.py to change it from python to python3.
Maybe we could just document that?
(Or would it work to use os.path.basename(sys.executable) ?)
On Sun, Apr 8, 2018 at 11:02 AM, Tom Forbes wrote:
> It may be an obstacle but I believe it’s better than having them nuke
> t
>
> (Or would it work to use os.path.basename(sys.executable) ?)
The shebang is interpreted by the OS so this is before python even starts :)
On 9 April 2018 at 20:53, Collin Anderson wrote:
> I personally just edit my manage.py to change it from python to python3.
> Maybe we could just docume
Hi,
We've been talking about it internally in my company and wanted to ask
about feedback for adding an --exit / --check option (similarly
to
https://groups.google.com/forum/#!searchin/django-developers/exit$20code|sort:date/django-developers/I3M6B-wYYd8/5sZY30VtlR4J)
for showmigrations comma
I'm thinking something like #!/usr/bin/env
{{ os.path.basename(sys.executable) }} when running startproject. (Though
on windows I that would be #!/usr/bin/env python.exe - not sure if that
would work or not)
On Mon, Apr 9, 2018 at 3:58 PM, Adam Johnson wrote:
> (Or would it work to use os.path.b
