With the latest trunk I actually had 4 unit test failures -- maybe my
setup is screwed. http://www.pastethat.com/VulU5
These happened either way though, the same errors.
On Dec 23, 9:03 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> On Dec 23, 2007 8:02 PM, David Cramer <[EMAIL PROTECTED]> w
Since assignment of variables is illegal in the template syntax, and
{% blocktrans %} cannot contain other tags (notably {% url %}), there
is a problem for marking strings as translatable which contain links
in them in django templates.
Sometimes you can get around it with something like {% block
On Oct 16 2006, 2:03 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> I've refactored Django's setup.py so that it uses the plain Python
> distutils installation method rather than ez_setup/setuptools. This
> means it no longer requires an Internet connection to install Django.
> Hooray!
From w
On Dec 23, 2007 8:02 PM, David Cramer <[EMAIL PROTECTED]> wrote:
> I was looking over some code today and noticed that the __new__
> definition of ModelBase does if x in dir(y). Doing some quick tests
> showed this was a lot slower than doing if hasattr(x, y). Is there any
> reason it's done like
I'm not 100% sure what the question is. Are you asking if the
additional fields on AlbumSongMap are accessible directly from the
Album or Song models? If so, then no that's not the case with the
current patch. It is however possible to use the QuerySet API to
query for Album or Song objects giv
I was looking over some code today and noticed that the __new__
definition of ModelBase does if x in dir(y). Doing some quick tests
showed this was a lot slower than doing if hasattr(x, y). Is there any
reason it's done like this?
http://www.pastethat.com/Qxayj
This is the specific group of line
Ya that's what I'm getting at.
You can filter, as per your example, but can you then access those
arguments? My example wasn't too good, as it's more of a generic
relation use case of what this is fixing.
On Dec 22, 11:44 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I not sure, but I thi
Ticket opened. http://code.djangoproject.com/ticket/6272
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscr
Just did a simple benchmark and found that Louie is about 150% slower
than current dispatcher in Django. It looks like Louie developers
doesn't care about performance at all...
On 23 дек, 16:49, Simon Willison <[EMAIL PROTECTED]> wrote:
> On 23 Dec 2007, at 12:39, ivan.illarionov wrote:
>
> > As
On Dec 23, 2007 12:13 AM, Jeff Anderson <[EMAIL PROTECTED]> wrote:
> I clicked on the login link in track (in case it brought me to a log
> in/create account page) That's not how trac works though. I ended up at
> this link:
> http://code.djangoproject.com/wiki/TracGuide
At the moment, AFAIK it's
On 23 Dec 2007, at 12:39, ivan.illarionov wrote:
> As I know PyDispatcher project has evolved into Louie project and is
> actively maintained by the same author. The code is *not* ugly, is
> closer to Django coding style and has a lot of improvements.
> http://louie.berlios.de/
>
> Even more, I
As I know PyDispatcher project has evolved into Louie project and is
actively maintained by the same author. The code is *not* ugly, is
closer to Django coding style and has a lot of improvements.
http://louie.berlios.de/
Even more, I replaced content of django.dispatch with louie code,
renamed a
12 matches
Mail list logo
