Re: #28779 needs qualified opinion from devs, customizing REDIRECT_FIELD_NAME is cumbersome

What I tried to suggest there is that if this problem affects you, please describe your use case and how you are currently solving the issue (if at all) and what changes you propose to make to Django to resolve the ticket. On Sunday, April 8, 2018 at 1:53:55 PM UTC-4, bukow bukowiec wrote: > > h

#28779 needs qualified opinion from devs, customizing REDIRECT_FIELD_NAME is cumbersome

https://code.djangoproject.com/ticket/28779 It was proposed to mention that ticket in the Developers Mailing list, so this is what i do :) Can someone qualified say? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself

Re: Shouldn't manage.py call python3 instead of python?

It may be an obstacle but I believe it’s better than having them nuke their base systems by accident by installing a package that conflicts with their base system. This isn’t such a huge issue on MacOS but on Linux it is and I’ve seen it happen a few times. Not to mention the issue of multiple conf

Re: Setting defaults in the DB to support zero-downtime migrations

I've found other places where things are fiddly for production migrations as well. Migrating a nullable to a non-nullable field is one of a range of cases where the migration cannot be run until the code has been fully deployed to no longer write nulls to the database. A similar case, that's even a

Re: Shouldn't manage.py call python3 instead of python?

I never really liked the idea of using VirtualEnv or HomeBrew over the default installation in Mac OS. (FreeBSD has the same naming issues). Having beginners use VirtualEnv or HomeBrew always struck me as a huge obstacle to getting a beginners Django developer's environment operational, as we

Re: Shouldn't manage.py call python3 instead of python?

This only seems to be an issue when you are using the base system interpreter to run manage.py. installing Django and other dependencies there is not recommended for a variety of reasons, and this isn't a problem when using a virtualenv, it doesn't seem like there is much to fix IMO. On Sun, 8 Ap

Re: Shouldn't manage.py call python3 instead of python?

Is it OK to reopen that ticket? The problem is that python2 and python3 need to coexist in most systems, and you can’t just rename python3 to python. -bobby > On Apr 6, 2018, at 8:30 PM, Tim Graham wrote: > > It was tried in https://code.djangoproject.com/ticket/27878 >