Re: discontinue shipping tests with contrib apps?

Hello, I find the flat structure in tests/ quite convenient, especially for making large changes, also in combination with shell globbing. Merging modeltests and regressiontests was a win. I'm not convinced a contrib folder would help much. Reserving foo_* for contrib app foo sounds sufficient

Re: User.username max_length 254

Yes please! Since contrib.auth.models.User.email is an EmailField, that change will require everyone to run a migration, right? Then we might as well change the character limit on the username field at the same time, no? And any other defaults that might be less-than-reasonable? I was going

Abstract models and the app registry

Hi all, I'm looking for some background about abstract models, specifically why they aren't registered with the app registry as normal models are. For some context, I'm working on a ticket [0] to refactor Django's lazy model operations (used e.g. to resolve string references in related fields). T

Re: Abstract models and the app registry

Hi Alex, On 02/11/2015 11:39 AM, Alexander Hill wrote: > I'm looking for some background about abstract models, specifically why > they aren't registered with the app registry as normal models are. > > For some context, I'm working on a ticket [0] to refactor Django's lazy > model operations (use

Bytecode in Migrations

I have gotten bitten by lingering bytecode in migrations on several occasions. Steps to reproduce are a little bit complex, but here is an rough example: Local Box: — have *.pyc rule in .gitignore — create some migrations — commit them Server Box: — pull repository — execute migrations Local B

Re: Bytecode in Migrations

Hah. Check out this ticket :) https://code.djangoproject.com/ticket/23406 On Wed, Feb 11, 2015 at 4:04 PM, abhillman wrote: > I have gotten bitten by lingering bytecode in migrations on several > occasions. Steps to reproduce are a little bit complex, but here is an > rough example: > > Local Bo

Re: Bytecode in Migrations

I am a little confused, Colin. I am running django 1.7.4, but seem to have come across an issue whereby lingering *.pyc files broke the "python manage.py migrate" command. But the ticket suggests that bytecode is in fact currently ignored. Do you know what's up here? Don't want to clutter up th

Re: Bytecode in Migrations

Just checked the source that I was using. Definitely 1.7.4 and the local version of django I have reads: 95 for name in os.listdir(directory): > 96 if name.endswith(".py"): > 97 import_name = name.rsplit(".", 1)[0] > 98 if im

Re: Bytecode in Migrations

Your problem is likely that the pyc file for the new initial migration somehow seems newer than the py file and so Python is using it over the new source file. I'm not sure how this happens if it's a new migration, but I've seen it happening when switching git branches before. We have pyc files tu

Re: Abstract models and the app registry

Hi Carl, Thanks for getting back to me. That all makes sense. I'm still curious as to why abstracts aren't registered – is that a requirement of some feature of the app registry design, or is it just that way because? I think what I would like to do is just declare that string references in r

Requesting eyeballs on a change to SQLite schema editor

Hi all, doing a bit of yak shaving here. I'm currently refactoring Django's lazy operations [0], and ran into a bit of a snag which led me to make some changes to SQLite's schema editor. All the tests pass, but I thought I should bring this up here to get a few more eyeballs on my changes since

Django inlineformset autocomplete and autopopulate by ajax

I'm trying to do this following link feature in django, http://demo.smarttutorials.net/jquery-autocomplete/ Here by choosing country the rest of the fields will be auto populated, like this i'm trying to achieve in django, If any idea pls tell me it will be very great for me This is Product ta