Hey Eric,
That's a very good idea. I've looked through the current management commands to
see what arguments they take. The most used variants are:
- no arguments
- custom list
- appname(s)
- fixture(s)
The problem with your proposal is the handling of multiple appnames and
fixtures (e.g. "dja
On Mar 17, 2010, at 3:35 PM, guillermooo wrote:
> autocomplete() is executed always, regardless whether the user has
> requested completions or not. The only early exit point of
> autocomplete() is reached if DJANGO_AUTO_COMPLETE is false. Otherwise,
> sys.exit(1) returns to the console. How is th
Hi,
I’m going to apply for GSoC with the goal of refactoring the app loading [0].
I’ve been looking at Django’s current app loading implementation
(db.models.loading), Vinay Sajip’s patch in #3591 [1] and the notes on the
InstalledAppsRevision wiki page [2]. Here's what I'm planning to change.
On Apr 7, 2010, at 1:40 PM, Russell Keith-Magee wrote:
> On Mon, Apr 5, 2010 at 5:35 AM, Arthur Koziel wrote:
>> Hi,
>> I’m going to apply for GSoC with the goal of refactoring the app loading
>> [0]. I’ve been looking at Django’s current app loading implementation
>>
On Apr 7, 2010, at 1:40 PM, Russell Keith-Magee wrote:
> I agree with Alex - there's a lot more detail needed here. How will I
> get access to the App instance that a model belongs to? How will
> legacy attributes like db_prefix be proxied? What is the order of
> precedence when a model and an app
Hey there,
my name is Arthur Koziel and I'll be working on the app loading refactor for
this year's gsoc program. I'm currently a business informatics student in
dortmund, germany and working towards my bachelor's degree.
I didn't get any coding done this week. I
Hey there,
I'm making some progress on the app loading gsoc project. I'm still in the
process of writing tests for the AppCache. It took me longer than I've thought.
However, I'm really confident that I'll finish the testing stuff this week and
move on to writing the new App class. There are st
Hey there,
sorry for not posting an update in such a long time. The hardest part of the
refactoring so far was keeping backwards compatibility. So while the internals
of the appcache changed, the functionality remained the same. Ayway, the
interesting stuff is still coming up. So there aren't a
Hey there,
the GSOC is over and I wanted to give you all a final status report.
The AppCache was refactored and now creates app instances instead of just
loading models. An app is either an instance of django.core.apps.App or a
custom class. This depends on the entry in the INSTALLED_APPS setti
es in INSTALLED_APPS
> or somewhere in settings supported now?
>
> On Mon, Aug 23, 2010 at 2:06 AM, Arthur Koziel
> wrote:
>> Hey there,
>>
>> the GSOC is over and I wanted to give you all a final status report.
>>
>> The AppCache was refactored and now
On Sep 9, 2010, at 7:24 AM, Javier Guerra Giraldez wrote:
> what about giving parameters to the apps? something like:
>
> INSTALLED_APPS = (
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.sites',
> 'django.c
Hey Alex,
thanks for taking the time to review the code. However, we've agreed not to
construct the app instances in the settings.py file as it would require
imports to be used, and stick to the convention of dotted paths. You might
want to read this thread [0], but especially this [1] reply from
Hey there,
I'm going to continue my work on the app loading branch when I finish my
exams end of February.
Oh, and the last discussion about this was 3 weeks ago:
http://groups.google.com/group/django-developers/browse_thread/thread/c8921795bc7868af/
Arthur
On Wed, Jan 19, 2011 at 8:27 PM, bend
13 matches
Mail list logo
