/code.djangoproject.com/ticket/4135#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django update
u using for the {{{openid_key}}} field?, is it a
!CharField? a !ForeignKey?. Please post [a fragment with relevant parts to
reproduce the problem of] your {{{models.py}}} file to the django-users
mailing list.
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:1>
Django Code <http:
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
_tests: 0| Needs_better_patch: 0
---+
Changes (by anonymous):
* cc: [EMAIL PROTECTED] (added)
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/3268#comment:15>
D
n remain simple text
input fields with either one.
--
Ticket URL: <http://code.djangoproject.com/ticket/3268#comment:16>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received t
a problem with this patch?
does it still work for your own form_for_models forms?
--
Ticket URL: <http://code.djangoproject.com/ticket/3268#comment:17>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~--
being unable to use patch
correctly. I should learn to double-check before updating any bugs. :-/
Apologies.
--
Ticket URL: <http://code.djangoproject.com/ticket/3268#comment:18>
Django Code <http://code.djangoproject.com/>
The web framework f
oject.com/ticket/3213#comment:10>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
atting i18n missing. (ie.
You cannot i18n the time formatting string) This simple patch resolves it.
--
Ticket URL: <http://code.djangoproject.com/ticket/4137>
Django Code <http://code.djangoproject.com/>
The web framework for perfectioni
| Needs_better_patch: 0
+---
Changes (by Simon G. <[EMAIL PROTECTED]>):
* status: new => closed
* resolution: => fixed
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/3213#comment:
Added some more translations
1. Includes two new translation messages with #4137
--
Ticket URL: <http://code.djangoproject.com/ticket/4138>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~--
ong in the
documentation for a long time.
--
Ticket URL: <http://code.djangoproject.com/ticket/4022#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this messa
jango-dev mailing
list.
--
Ticket URL: <http://code.djangoproject.com/ticket/4129#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are sub
cs: => 0
Comment:
Please ignore the first patch. The second has some unneccesary 'fuzzy'
status removed.
--
Ticket URL: <http://code.djangoproject.com/ticket/4138#comment:1>
Django Code <http://code.djangoproject.com/>
The web
chapter10/ Django book] also
mentions this (but I can't make a comment on it now as it is closed to
comments).
The fix would obviously be to correct the text at the first link.
--
Ticket URL: <http://code.djangoproject.com/ticket/4139>
Django Code <http://code.djangop
_patch: 0
--+-
Changes (by SmileyChris):
* stage: Unreviewed => Accepted
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4139#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perf
_patch: 0
--+-
Comment (by SmileyChris):
Don't think that was the revision where it was removed, but it's
definitely not there now in any case.
--
Ticket URL: <http://code.djangoproject.com/ticket/4139#comment:2>
Django Code <http://cod
but unique field
which holds a string.
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this
n it's blank. At least if the field is set to
null=True. In reality a string being '' is the same as being empty. I have
no problems with this except for the admin interface.
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:4>
Django Code <http://code.d
openid support in
django or not. Not about whether there is an implementation or not.
--
Ticket URL: <http://code.djangoproject.com/ticket/3213#comment:12>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~
for checkin
* needs_tests: => 0
* needs_docs: => 0
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4137#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~-
re, but we aren't going to start
automatically storing NULLs.
--
Ticket URL: <http://code.djangoproject.com/ticket/4136#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~
ngoproject.com/ticket/4133#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django updates" g
+---
Comment (by [EMAIL PROTECTED]):
Hah! Yes, that fixes it. Thanks :)
--
Ticket URL: <http://code.djangoproject.com/ticket/4022#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists wi
about"
(with note about have restructured text package installed). It doesn't
require a script.
--
Ticket URL: <http://code.djangoproject.com/ticket/4034#comment:2>
Django Code <http://code.djangoproject.com/>
The web fra
-+--
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
This is just a bug. No discussion required.
--
Ticket URL: <http://code.djangoproject.com/ticket/4129#comment:6>
Django C
ag", since it's
not that hard to do so and it's a corner-case. Want to think about it some
more, though.
--
Ticket URL: <http://code.djangoproject.com/ticket/4031#comment:2>
Django Code <http://code.djangoproject.com/>
The web framew
;s too much fine-tuning to ship by default,
though.
--
Ticket URL: <http://code.djangoproject.com/ticket/4028#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received t
you need to write an external copy()
function that handles this.
Seems like a reasonable thing to do, so feel free to knock up a patch. A
method on the Model class wouldn't be insane.
--
Ticket URL: <http://code.djangoproject.com/ticket/4027#comment:4>
Django Code <http://code.
think any changes are needed here.
--
Ticket URL: <http://code.djangoproject.com/ticket/4007#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message becaus
practice is that select names should be
descriptive enough on their own. You might want to post it to Django
snippets, though, for people who would find this useful.
--
Ticket URL: <http://code.djangoproject.com/ticket/4003#comment:2>
Django Code <http://code.djangoproject.com/&g
so be usable for all forms, not just the admin interface.
--
Ticket URL: <http://code.djangoproject.com/ticket/3990#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You
cision needed => Accepted
Comment:
Let's see how simple the patch looks. Should be a reasonable change.
--
Ticket URL: <http://code.djangoproject.com/ticket/3989#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for per
ably
about +0.5 on this.
The patch needs improvement, though. There must be a less messy way to
write the change at line 88.
--
Ticket URL: <http://code.djangoproject.com/ticket/3985#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for p
hink this is also bumping up against row-level permissions, so it
really does need a list discussion, doing a compare and contrast with that
branch.
Closing again for all the above reasons.
--
Ticket URL: <http://code.djangoproject.com/ticket/3984#comment:5>
Django Code <http://code.d
ight seem like an easy thing to do,
but it increases the maintenance burden and isn't always really scratching
more than just an isolated itch. I think in this case, it's not worth
including.
--
Ticket URL: <http://code.djangoproject.com/ticket/3963#comment:4>
Django Code &l
mtredinnick):
* stage: Design decision needed => Accepted
Comment:
These should be removed.
--
Ticket URL: <http://code.djangoproject.com/ticket/3960#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists
flawed, so it does
have a backwards-incompatibility impact, however it's not like 1.0 isn't
going to have a few of those.
--
Ticket URL: <http://code.djangoproject.com/ticket/3959#comment:3>
Django Code <http://code.djangoproject.co
18N=False.
--
Ticket URL: <http://code.djangoproject.com/ticket/3940#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
s normal.
--
Ticket URL: <http://code.djangoproject.com/ticket/3857#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Go
go against the grain.
--
Ticket URL: <http://code.djangoproject.com/ticket/3993#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subsc
---+
Changes (by mtredinnick):
* status: reopened => closed
* resolution: => wontfix
Comment:
The more compact form is not greatly more readable. Let's leave it as
nested tags.
--
Ticket URL: <http://code.djangoproject.com/ticket/3826#com
--+-
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
This is a reasonable change. I've wondered about making it in the past.
--
Ticket URL: <http://code.djangoproject.com/ticket/3842#comment:2&g
et URL: <http://code.djangoproject.com/ticket/3771#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django u
of data withour edit
permissions) can now handled by the shiny new
[http://www.djangoproject.com/documentation/databrowse/ databrowse]
package.
--
Ticket URL: <http://code.djangoproject.com/ticket/3984#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for p
ond run of manage py syncdb goes without error.
--
Ticket URL: <http://code.djangoproject.com/ticket/4140>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are su
) and psycopg 2.0 (self-compiled)
--
Ticket URL: <http://code.djangoproject.com/ticket/3201#comment:8>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because yo
Unreviewed => Design decision needed
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/3119#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received t
ute
19. self.db.queries.append({
UnicodeDecodeError at /admin/aggregator/userprofile/1/
'ascii' codec can't decode byte 0xc5 in position 511: ordinal not in
range(128)
}}}
Maybe this can be fixed only with the Unicode branch?
--
Ticket URL: <http://code
):
* needs_better_patch: => 0
* version: SVN => 0.96
* needs_tests: => 0
* needs_docs: => 0
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4142#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfe
a `Form` I was using. If it violates what's expected, don't worry about
it; either I'll come up with something else or just continue to patch it
solely on my installation :)
--
Ticket URL: <http://code.djangoproject.com/ticket/3993#comment:4>
Django Code <http://code.djang
AIL PROTECTED]>):
* status: new => closed
* resolution: => duplicate
Comment:
dup of #4013.
--
Ticket URL: <http://code.djangoproject.com/ticket/4142#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfe
x27;s time.
--
Ticket URL: <http://code.djangoproject.com/ticket/4020#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribe
loyee" that
extends Person) is in flux--perhaps it was supported to some extent in
past revisions, but is being changed? At any rate, for people coming to
Django from other frameworks it'd be helpful if in your FAQ you could
address the issue.
--
Ticket URL: <http://code.djangopro
+---
Changes (by Gary Wilson <[EMAIL PROTECTED]>):
* status: reopened => closed
* resolution: => invalid
Comment:
No bug here.
--
Ticket URL: <http://code.djangoproject.com/ticket/4022#comment:7>
Django Code <http://code.djangoproject.co
n is are we
perfectionists to the level of breaking backwards compatibility?
(I'm +0 too)
--
Ticket URL: <http://code.djangoproject.com/ticket/3959#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for p
doing some database calls. See http://dpaste.com/hold/8999/
--
Ticket URL: <http://code.djangoproject.com/ticket/4146>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this
://www.djangoproject.com/documentation/0.96/tutorial03/
--
Ticket URL: <http://code.djangoproject.com/ticket/4142>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message bec
this
check is really only used within that `if` statement, and it seems it
could just as easily go there without any trouble.
--
Ticket URL: <http://code.djangoproject.com/ticket/4144>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
-
Comment:
I couldn't add the attachment, it crashed everytime, so the localflavor
files can be found at http://einaregilsson.com/downloads/is.zip
--
Ticket URL: <http://code.djangoproject.com/ticket/4143#comment:1>
Django Code <http://code.djangoproject.com/>
The web framewo
out the format 'S' that adds the
ordinals (1st, 2nd etc) but I don't know how other languages deal with
this.
I can submit a patch for this...
--
Ticket URL: <http://code.djangoproject.com/ticket/4147>
Django Code <http://code.djangoproject.com/>
The web framework
ds_tests: => 0
* summary: FileField.upload_to issues => dynamic destinations for
FileField.upload_to
* version: 0.96 => SVN
* needs_docs: => 0
* stage: Unreviewed => Design decision needed
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/
* needs_tests: => 0
* needs_docs: => 0
Comment:
That's the last time I create a diff by hand because I don't have proper
diff tools here at work. I'll fix it when I get home.
--
Ticket URL: <http://code.djangoproject.com/ticket/4144#comment:1>
Django Code <http
was just consistency. This would
fall in line with `verbose_name`, and thus make Django feel a bit more
unified, that's all. So like I said, I'm +0 really, I'm not going to lose
sleep over this one.
--
Ticket URL: <http://code.djangoproject.com/ticket/3959#comment:4>
Django C
racle behavior we can't fix, but we could perhaps
put in a check somewhere for SQL reserved words as column names so that
the problem is flagged earlier, with an informative message.
--
Ticket URL: <http://code.djangoproject.com/ticket/4140#comment:1>
Django Code <http://cod
the unicode branch.
I'll leave this open until that is merged, but it's not something to fix
on trunk.
--
Ticket URL: <http://code.djangoproject.com/ticket/4141#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework
ode.djangoproject.com/ticket/4143>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django updates" gro
+---
Changes (by Gary Wilson <[EMAIL PROTECTED]>):
* status: new => closed
* resolution: => fixed
Comment:
It appears the redirect is now in place, closing ticket.
--
Ticket URL: <http://code.djangoproject.com/ticket/3992#comment:5>
to maintain this,
since this looks like it'll be a fairly robust project on its own. In
short: I'm happy with this. However, if you do want this moved into
Django, then it's best to raise this issue in the developers group.
--
Ticket URL: <http://code.djangoproject.com/ticket/
: 0
---+
Changes (by Gary Wilson <[EMAIL PROTECTED]>):
* cc: [EMAIL PROTECTED] (added)
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/3297#comment:44>
Djang
he patch based on comments, as I would like this as
well :)
--
Ticket URL: <http://code.djangoproject.com/ticket/3185#comment:21>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You
e if I'm just missing it, but where exactly is the problem?
You're not giving much in the way of details :)
--
Ticket URL: <http://code.djangoproject.com/ticket/4146#comment:1>
Django Code <http://code.djangoproject.com/>
The web
better, IMO
:)
--
Ticket URL: <http://code.djangoproject.com/ticket/4131#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
patch: 0
+---
Changes (by Collin Grady <[EMAIL PROTECTED]>):
* has_patch: 0 => 1
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4067#comment:2>
Django Code <http://code.
f any)
the actual problem is - Chris, I recommend opening a new ticket regarding
this which clearly explains a specific bug or enhancement to how
`filter()` works.
--
Ticket URL: <http://code.djangoproject.com/ticket/3587#comment:7>
Django Code <http://code.djangoproject.com/>
value will have to update their settings.
--
Ticket URL: <http://code.djangoproject.com/ticket/4049#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this mess
+---
Changes (by Michael Axiak <[EMAIL PROTECTED]>):
* cc: [EMAIL PROTECTED] (added)
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/2070#comment:110>
Django Code <http://code.djangoproject.com/>
look like a bug to me unless I'm missing something.
You can't have two generic or foreign keys with identical `related_name`s
pointing to the same model.
--
Ticket URL: <http://code.djangoproject.com/ticket/2573#comment:1>
Django Code <http://code.djangoproject.com/>
The
vironment is pulling one over the other
--
Ticket URL: <http://code.djangoproject.com/ticket/4146#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this
stays on a site like djangosnippets, where it could
really help people who plan to generate PDFs.
--
Ticket URL: <http://code.djangoproject.com/ticket/4148>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~--
--
Ticket URL: <http://code.djangoproject.com/ticket/4148#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"
ts: 0 | Needs_better_patch: 0
-+--
Changes (by Michael Axiak <[EMAIL PROTECTED]>):
* needs_docs: 1 => 0
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4148#comment:2&
eware to fix IE VARY bug
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4148#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message be
(by SmileyChris):
* status: closed => reopened
* resolution: duplicate =>
Comment:
Actually, that other ticket was user error, this ticket is the correct
one.
--
Ticket URL: <http://code.djangoproject.com/ticket/2713#comment:2>
Django Code <http://code.djangoprojec
on)
sect = cache_page(sect, 60)
}}}
This is actually a documentation bug (or the decorator format needs to
change), but I'll submit a new ticket for that.
--
Ticket URL: <http://code.djangoproject.com/ticket/2564#comment:5>
Django Code <http://code.djangoproje
;s just fix the
documentation.
--
Ticket URL: <http://code.djangoproject.com/ticket/4149>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
cide that for sure.
--
Ticket URL: <http://code.djangoproject.com/ticket/2713#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are
+---
Comment (by SmileyChris):
Actually, thinking some more about this, this has been fixed by named url
patterns (see [4901])
--
Ticket URL: <http://code.djangoproject.com/ticket/2713#comment:4>
Django Code <http://code.djangoproject.
+---
Changes (by SmileyChris):
* status: reopened => closed
* resolution: => fixed
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/2713#comment:5>
Django Code <http://code.djangoproject.com/>
The
Needs_tests: 0 | Needs_better_patch: 0
+---
Comment (by SmileyChris):
New ticket: #4919
--
Ticket URL: <http://code.djangoproject.com/ticket/2564#comment:6>
Djang
ually going wrong
2. What you would expect to happen instead
--
Ticket URL: <http://code.djangoproject.com/ticket/4146#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
Yo
e-case, I validated that this does raise the
above exception and that the patch fixes this.
--
Ticket URL: <http://code.djangoproject.com/ticket/2608#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfecti
icket/4149#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To pos
t.
--
Ticket URL: <http://code.djangoproject.com/ticket/2564#comment:7>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
before /
after screenshots but trac won't let me.
Probably needs some more testing to make sure this doesn't break any
existing fields.
--
Ticket URL: <http://code.djangoproject.com/ticket/2612#comment:1>
Django Code <http://code.djangoproject.com/>
The web frame
t:8>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send e
fix IE VARY bug
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4148#comment:4>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you a
d only check `sys.modules` when it
needs to => ModelBase should only check
`sys.modules` when it needs to
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4144#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for pe
Comment:
--
Ticket URL: <http://code.djangoproject.com/ticket/4134#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed
//code.djangoproject.com/ticket/4131#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django updates&q
101 - 200 of 18926 matches
Mail list logo