Re: Must a Django Database Support Migrations?

Hi Marcin, I don't believe it's some sort of ethos that got Andrew to collaborate with Django and create the current migration framework: It's the fact that pretty much everyone who used Django also used South that convinced Andrew to recreate its behaviour as a core Django app. I'm not saying

Re: Potentially inconsistent behavior between test client and normal WSGI requests

I've checked against the wsgiref module and you are most certainly correct: unquoting PATH_INFO is the job of the wsgi server. I'll being up the issue with with the aiohttp folks. Thanks for your time. On Saturday, April 25, 2015 at 3:02:50 AM UTC-4, Florian Apolloner wrote: > > > > On Saturda

Re: Must a Django Database Support Migrations?

On Sun, Apr 26, 2015 at 8:33 PM, Marcin Nowak wrote: > Hi. > > Before v1.7 there were no migrations and Django was quite useful (for > example with South as an 3rd party app). What happened then? > > I think that migrations can be decoupled from core and you just don't want > to do this for some

Re: Idea/request for help: Django Developers Community Survey

The idea of the release schedule question is to form consensus on the options that have already been proposed in the "1.9 release planning " thread. If you have a different idea, please propose it there. On Sunday, Apri

Re: Must a Django Database Support Migrations?

Hi. Before v1.7 there were no migrations and Django was quite useful (for example with South as an 3rd party app). What happened then? I think that migrations can be decoupled from core and you just don't want to do this for some unknown reason. I'll prepare a pull request if it will not be d

Re: Setting database default values in migrations (postgres)

Simply do not use Django builtin migrations. Consider using Liquibase (maybe with Liquimigrate wrapper for Django) and feel freedom. BR Marcin On Thursday, October 30, 2014 at 4:47:18 PM UTC+1, Peter Coles wrote: > > Hey all, > > I'm interested in getting database migrations to support setting

Re: Setting database default values in migrations (postgres)

Greetings, I know this is an old thread, but it's an issue I am coming up against and hopefully I can restart the conversation. I do think it's important that we use as many native database features as possible for application portability, extensibility, and performance. I have a different sol

Re: Idea/request for help: Django Developers Community Survey

I like the idea of an survey, but find the release question with only 3 options quite limited, how about to allow there to put own numbers instead of giving fixed answers or at least an other field? Am 25.04.2015 14:29, schrieb Tim Graham: Aymeric and I put together a draft: https://docs.goog

Re: Idea/request for help: Django Developers Community Survey

Hi, "How often would you like to see new major version of Django released?" currently lists three options, which are close to one another. I would like to have: 12 months, as well as an open option. Is it an idea to add those? Detailed release schedules are not necessary, in my opinion. "I foll