On Wed, Oct 1, 2008 at 4:04 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> The thing is, it's a really nice place to emit a signal if you want to
> do things "just after things are ready", but there's no signal for it.
Just after *what* is ready, precisely? After "import django" has
succeeded? Afte
Marc Fargas schrieb:
> Hi there,
>
> Staring at #8638 I'm trying to find a way to hook code to be run "just
> after Django is completelly loaded" and found no way ;(
>
...
> So, would a signal there be useful?
I am missing this signal, too.
Thomas
--
Thomas Guettler, http://www.thomas-guett
On Wed, Oct 1, 2008 at 5:04 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
>
>
> So, would a signal there be useful? (no ticket filled yet) And, where
> can one hook code for that? :)
>
I seem to recall this request being made from time to time. IIRC, it
always turned out that whoever asked didn't re
Hi all,
Now that the trunk is open for enhancements, I would like to ask the
core developers for their opinion on ticket 8122: better way of
testing for cookies [1]. Chris Beaven looked at the ticket and
suggested I bring it up here to solicit comments.
The ticket addresses the awkward set_test_
On Wed, Oct 1, 2008 at 2:04 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> So, would a signal there be useful? (no ticket filled yet) And, where
> can one hook code for that? :)
I don't think any such place exists, so there's nothing you can do for it.
--
Collin Grady
--~--~-~--~~---
Hi there,
Staring at #8638 I'm trying to find a way to hook code to be run "just
after Django is completelly loaded" and found no way ;(
The thing is, it's a really nice place to emit a signal if you want to
do things "just after things are ready", but there's no signal for it.
And, as I found
Hi ppl,
In the contributing docs we can read:
After a branch has been merged, it should be considered "dead";
write access to
it will be disabled, and old branches will be periodically "trimmed."
My English is not very good but I always understood that as "we'll
remove them when they ge
Hi,
On Wed, Oct 1, 2008 at 12:57 PM, Thomas Guettler <[EMAIL PROTECTED]> wrote:
> #689 Honour Webserver Provided Auth (REMOTE_USER)
> http://code.djangoproject.com/ticket/689
> Why not commit it?
It's submited as candidate for 1.1, hopefully it can get it ;) Altough
that means I would not longe
On Wed, Oct 1, 2008 at 4:07 AM, Richard Davies
<[EMAIL PROTECTED]> wrote:
> Perhaps it's now time for a '1.0.1' milestone in the ticket tracker,
> to nominate those tickets which are simple bug fixes against '1.0'?
No.
Right now any bug at all that was present in 1.0 is a candidate for fixing.
Please move this conversation to django-users. Django-developers is for the
discussion pertaining to the maintenance and development of the django
framework itself.
On Thu, Oct 2, 2008 at 3:55 AM, Erik Allik <[EMAIL PROTECTED]> wrote:
>
> Nevermind the previous e-mail.
>
> On 01.10.2008, at 17:10
Nevermind the previous e-mail.
On 01.10.2008, at 17:10, David Hall wrote:
>
> I've just released an open-source version control application for
> Django. It is available for download from Google code.
>
> http://code.google.com/p/django-reversion/
>
> Features include:
>
> - Roll back to any p
Hi David,
Is this integrate with Subversion or any Version Control Tool?
Regards,
-LN
On Wed, Oct 1, 2008 at 10:10 AM, David Hall <[EMAIL PROTECTED]> wrote:
>
> I've just released an open-source version control application for
> Django. It is available for download from Google code.
>
> http:/
Is it an alternative to django-evolution and dmigrations? If not, does
it provide a subset of the features of the two?
Erik
On 01.10.2008, at 17:10, David Hall wrote:
>
> I've just released an open-source version control application for
> Django. It is available for download from Google code
I've just released an open-source version control application for
Django. It is available for download from Google code.
http://code.google.com/p/django-reversion/
Features include:
- Roll back to any point in a model's history - an unlimited undo
facility!
- Recover deleted models - never
Hi everybody, and first thanks to everyone involved in Django's
developpement.
I recently discovered that when extending a base template,
templatetags outside a block node in the 'extending' template where
just ignored. This of course makes perfect sense for content-rendering
tags, but can be a p
On Wed, Oct 1, 2008 at 12:17 PM, Brett H <[EMAIL PROTECTED]> wrote:
>
> I cringe at posting this but.. there's a little forward slash that
> suddenly appeared on the Django website documentation url
>
> http://docs.djangoproject.com/en/dev//
>
> Is it just visiting or should I re-bookmark?
This i
I cringe at posting this but.. there's a little forward slash that
suddenly appeared on the Django website documentation url
http://docs.djangoproject.com/en/dev//
Is it just visiting or should I re-bookmark?
--~--~-~--~~~---~--~~
You received this message becaus
Hi,
#689 Honour Webserver Provided Auth (REMOTE_USER)
http://code.djangoproject.com/ticket/689
I use it this patch since several weeks. This patch only adds new
stuff, thus it wont' break running code.
Why not commit it?
Thomas
PS: The current code is in a git repository linked in the ticke
Great!
Perhaps it's now time for a '1.0.1' milestone in the ticket tracker,
to nominate those tickets which are simple bug fixes against '1.0'?
Clearly still too early for '1.1' milestone, etc, given that there's a
different process started for that
Cheers,
Richard.
--~--~-~--~
Streaming/iterable HttpResponse instances are kind of an issue which
needs sorting out. I've had problems in the past with the current
implementation. Maybe a closer look is actually necessary.
Regards,
Zack
On Oct 1, 3:41 am, David Cramer <[EMAIL PROTECTED]> wrote:
> Thanks Graham, I'll check t
> Short version: model-aware validation is being worked on. We didn't get
> it finished for 1.0, but it's still ongoing work.
Wouldn't it be nice to replace these three parameters by something like:
class SomeModel(models.Model):
[...]
class Meta:
unique_together = ('title', 'pub_
21 matches
Mail list logo