Steve Holden wrote:
> Jacob Kaplan-Moss wrote:
>> On Fri, Sep 19, 2008 at 2:19 AM, Steve Holden <[EMAIL PROTECTED]> wrote:
>>
>>> The question is: is it worth continuing this web-scraping and analysis
>>> and potentially extending it to other reference mechanisms I am unaware
>>> of? I don't
Jacob Kaplan-Moss wrote:
> On Fri, Sep 19, 2008 at 2:19 AM, Steve Holden <[EMAIL PROTECTED]> wrote:
>
>> The question is: is it worth continuing this web-scraping and analysis
>> and potentially extending it to other reference mechanisms I am unaware
>> of? I don't know whether the current
I have added a ticket with a patch
http://code.djangoproject.com/ticket/9159
On Sep 20, 11:27 am, HenrikV <[EMAIL PROTECTED]> wrote:
> The testing client is great for testing the whole request chain. It
> doesn't seem to support
> testing of middleware very well though. I think it should be
Oh, and by the way, with regards to thread safety, changes should be
made in the context, not the node. I'm currently working on a refactor
of the template system at the moment, something will be done within a
couple of days. If it's really necessary (I mean, I'm just doing it
for fun, but it
I see your point about overriding reusable app media.
I got an idea though when reading your post. Since people want to
update reusable apps to a more recent version/revision and since that
means the media files will/might change, why not add another command
that would show which installed
On Sep 20, 6:58 am, Erik Allik <[EMAIL PROTECTED]> wrote:
> Has anyone got some good use cases where the template-loaded mimicking
> behavior would be desired? Otherwise it's just needless complexity in
> my opinion.
Well, first of all, it's not really complexity at all. If it were to
just
> If multiple apps provide a media file of the same name, use the file
> provided by the app listed first in INSTALLED_APPS - this mimics the
> template loader behavior. In interactive mode (-i), you may specify
> which app to select from for each such file. With this command, best
> practice
The testing client is great for testing the whole request chain. It
doesn't seem to support
testing of middleware very well though. I think it should be improved
to support two approaches:
1) Directly calling the middleware functions passing a request and
response.
2) Calling the middleware as
I am working on #3011, making the User model overridable. I have a
working patch, but
if I set the db_table on the User model, the queryset and syncdb
doesn't seem to agree
on what the m2m table should be called.
As a sidenote there seems to a problem with certain combinations
db_table and
Probably the best thing to do, if anything, is to make something new
and get it working alongside the old system, much like "oldforms" and
"newforms" in 0.96. That way you keep backwards compatibility but
people can also leverage new features in their code.
Regards,
Zack
On Sep 20, 3:48 am,
Hi Jacob,
I agree that this is documented behavior for PostgreSQL
_transactions_.
The reason that I think it's a bug is that I shouldn't be in a
transaction at all - as I understand
http://docs.djangoproject.com/en/dev/topics/db/transactions/
, the default behaviour should be auto-commit in
11 matches
Mail list logo
