;https://code.djangoproject.com/ticket/14678#comment:8>
Django <https://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 email to django
her common use cases. For example, I'm not sure why logging to files as
I have it set records useful info, but the emailed version is essentially
blank!
It sounds like the Python docs talk about this in a lot more detail so we
shouldn't duplicate that but I think it wouldn't be bad to expand t
` supposed to have a comma?
--
Ticket URL: <https://code.djangoproject.com/ticket/16076#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Djan
et URL: <https://code.djangoproject.com/ticket/10870#comment:18>
Django <https://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
for the report. Just uploaded the fixed
patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/16076#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
&qu
[16410]:
{{{
#!CommitTicketReference repository="" revision="16410"
Fixed #16200 -- Stopped TemplateIfParser from returning something in
`__init__`. Thanks, traff.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16200#comment:4>
Django <https://code.djangoproject.com/>
}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16221#comment:4>
Django <https://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 grou
omment:
In [16412]:
{{{
#!CommitTicketReference repository="" revision="16412"
Fixed #16031 -- Corrected comments template examples. Thanks, teraom.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16031#comment:13>
Django <https://code.dj
[16413]:
{{{
#!CommitTicketReference repository="" revision="16413"
Fixed #16057 -- Extended deployment documentation with instructions for
uWSGI. Thanks, jpic and aaugustin.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16057#comment:5>
Django <https://code.dj
* resolution: => fixed
Comment:
In [16414]:
{{{
#!CommitTicketReference repository="" revision="16414"
Fixed #15908 -- Mention blocktrans in the pluralize filter documentation
section. Thanks, Julien Phalip.
}}}
--
Ticket URL: <https://code.djangoproject.co
pace to ease the use of jQuery plugins. The
`django.jQuery` object is still supposed to be used by Django's own
JavaScript files. Refs #12882.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/12882#comment:28>
Django <https://code.djangoproject.com/>
The Web framework for perfect
[16416]:
{{{
#!CommitTicketReference repository="" revision="16416"
Fixed #15127 -- Properly copy the choices of choice fields. Thanks, dready
and Julian Phalip.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/15127#comment:7>
Django <https://code.djangoproject.com/>
to schmichael and moopet.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14020#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django
code.djangoproject.com/ticket/12375#comment:10>
Django <https://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 email to
omment:
In [16419]:
{{{
#!CommitTicketReference repository="" revision="16419"
Fixed #9588 -- Allow passing kwargs to
`GenericInlineModelAdmin.get_formset` just like the InlineModelAdmin.
Thanks, prestontimmons.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/9
elMaries
and Bas Peschier.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/10802#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django update
from that ''contrib/session/tests.py'' need future imports for the with
statement.
--
Ticket URL: <https://code.djangoproject.com/ticket/16199#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message
ybe this is just the case. BTW, I recreated this bug in 1.3.
--
Ticket URL: <https://code.djangoproject.com/ticket/7198#comment:21>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to th
' problem
Environment:
Request Method: GET
Request URL: http://172.16.13.46:8080/addRecord/
Django Version: 1.3
Python Version: 2.6.6
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib
#13161: Ticked 2514 and 5171, solution for using Django with other psycopg2
applications.
-+-
Reporter: spoksss| Owner: nobody
Type: Bug| Status: new
ceback (most recent call last):
File "C:\home\dev\seka\seka\manage.py", line 14, in
execute_manager(settings)
File "C:\home\python\lib\site-
packages\django\core\management\__init__.py", line 438, in execute_manager
utility.execute()
File "C:\home\python\
letely unrelated to Django, let alone to the ticket you reopened.
This tracker is not the right place to discuss Python usage problems.
Please ask such questions in a Python developers forum / chat instead.
PS: my guess is that `someurl` is `None`.
--
Ticket URL: <https://code.djangopr
nd Julien for further work on
final patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/8999#comment:14>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google G
tly, the definition of a django application is: a package that
contains a module named "models". For instance, see the note in
https://docs.djangoproject.com/en/1.3/ref/settings/#installed-apps
I suppose this hasn't gotten much attention because people consider it's
part of the learning cu
#16255: Drop support for Posgres versions < 8.2 for Django 1.4
-+-
Reporter: ramiro | Owner: nobody
Type: | Status: closed
Cleanup/optimizat
sed not to
depend on contrib apps.
The root cause of the problem is the fact that since r14563
`django.core.management.validation` depends on
`django.contrib.contenttypes`. I am going to update the summary to reflect
this.
--
Ticket URL: <https://code.djangoproject.com/ticket/16283#comment:6&g
#5831: Template Debug highlights wrong {% for %} tag
-+-
Reporter: Charmless | Owner: vladmos
<jim-django@…> | Status: new
Type
e "untranslated language" in
`django.core.management.base.execute()`. The comment dates back to #5898,
which was a refactoring, so it may be even older. It would be nice to
check what's happening there too, and add an helpful comment for future
developers :)
--
Ticket URL: <https://code.djangoproject.com/
ody
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/16284#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
&quo
AIL: testRenderCommentFormFromObjectWithQueryCount
(regressiontests.comment_tests.tests.templatetag_tests.CommentTemplateTagTests)
--
Traceback (most recent call last):
File "/Users/myk/Desktop/django-
trunk/tests/regressiontests/comment_tes
=> 1
Comment:
The new behaviour needs to be optional to be backwards compatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/13252#comment:16>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this mess
/AndrewIngram/django-extra-
views/blob/master/extra_views/advanced.py
--
Ticket URL: <https://code.djangoproject.com/ticket/16256#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you ar
ter on in the response. Since we're
encouraging users to store lots of data in the cookie here, we should help
them when they store too much.
--
Ticket URL: <https://code.djangoproject.com/ticket/16199#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for
ing any data on
the backend, and a previously signed cookie is still technically valid
until it expires even if we've rotated it on the users end.
--
Ticket URL: <https://code.djangoproject.com/ticket/16182#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfe
: <https://code.djangoproject.com/ticket/16199#comment:12>
Django <https://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
and 100 of the signing module indicate that the provided salt is
used to prevent brute forcing. This is misleading, it's actually necessary
for namespacing signed strings, so that users can't take a signed string
from one part of Django and put it into a different part which will trust
it since
/ticket/13956#comment:16>
Django <https://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 email to django-updates@googl
.
Anyone care to weight in on this?
Being the logic the same in both implementations we might argue that the
probability of it being correct is somewhat high =)
--
Ticket URL: <https://code.djangoproject.com/ticket/16256#comment:14>
Django <https://code.djangoproject.com/>
The W
L: <https://code.djangoproject.com/ticket/13956#comment:17>
Django <https://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 grou
.
--
Ticket URL: <https://code.djangoproject.com/ticket/13956#comment:18>
Django <https://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
.
I accept the ticket because the second use-case sounds useful.
I set "patch needs improvement" because I'd like to make sure we don't
dismiss the first one too quickly.
--
Ticket URL: <https://code.djangoproject.com/ticket/16285#comment:1>
Django <https://code.django
ject.com/ticket/16199#comment:13>
Django <https://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 email
, I don't see that here).
Yeah, full agreement here, it felt wrong when I moved it over to using
pickle yesterday and wouldn't mind having a small abstraction (or
additional argument) for the loads/dumps functions.
--
Ticket URL: <https://code.djangoproject.com/ticket/16199#comment:14>
Djan
#16206: DB router example causes bug in django admin delete
--+---
Reporter: foxwhisper | Owner: nobody
Type: Bug | Status: closed
Milestone
ree with Paul's argumentation. Reverting seems
like the only option to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/16182#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you
problems, could you test whether ticket #16281 solves your problem?
--
Ticket URL: <https://code.djangoproject.com/ticket/16088#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed t
-
Ticket URL: <https://code.djangoproject.com/ticket/16160#comment:5>
Django <https://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
; 0
* easy: => 0
Comment:
#16160 reported another use case for changing the post-sync signals.
--
Ticket URL: <https://code.djangoproject.com/ticket/7561#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received th
docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/16184#comment:1>
Django <https://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
needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+---
Comment (by bpeschier):
mysql 5.0.51/py2.5
Normal run:
{{{
bpeschier@zeratul:~/dev/python/django/tests$ ./runtests.py
--settings
.
In case of models composite fields that are managed by a single virtual
field it would be useful to be able to supply a form field in ModelForms.
Currently the only virtual field in Django is GenericForeignKey and it
doesn't need this feature because each local field it relies
needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+---
Comment (by ojii):
Ran the tests manually now and get the following:
{{{
jenkins@pony:~/jobs/Django/workspace/database/mysql/python
needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
+---
Comment (by jezdez):
Seems like a caching issue to me, running the postgres tests gives me the
same:
{{{
[~/Code/git/django/tests
Ticket URL: <https://code.djangoproject.com/ticket/16213#comment:11>
Django <https://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 t
timing problems, merely reducing their probability (and possibly
hiding some nasty bugs).
--
Ticket URL: <https://code.djangoproject.com/ticket/16182#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message
[16356]. See #16182.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16182#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates"
ticket
as wontfix.
--
Ticket URL: <https://code.djangoproject.com/ticket/16182#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates"
that Django
will be installed into a site-packages directory, but this isn't a
reliable assumption.
Notably, Debian, Ubuntu etc will put it into a dist-packages directory,
and the tip to use:
{{{
python -c "from distutils.sysconfig import get_python_lib; print
get_python_lib()"
}}}
uggestion have been?
--
Ticket URL: <https://code.djangoproject.com/ticket/16287#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates
print get_python_lib()"'' returns:
/usr/lib/python2.6/dist-packages
whereas Django 1.2.4 installed from the tarball using python setup.py
install ''actually'' went into:
/usr/local/lib/python2.6/dist-packages
In other words, not the same dist-packages.
Meanwhile site-packages:
://groups.google.com/group
/django-developers/browse_thread/thread/d96e0121dad4476a
--
Ticket URL: <https://code.djangoproject.com/ticket/16288>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you ar
}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16099#comment:14>
Django <https://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
ention this behaviour.
--
Ticket URL: <https://code.djangoproject.com/ticket/16287#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates"
ils do not easily surrender their local install path, so I
added a paragraph to the docs about the location of site-packages.
--
Ticket URL: <https://code.djangoproject.com/ticket/16287#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
Ticket URL: <https://code.djangoproject.com/ticket/16288#comment:1>
Django <https://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.
around potentially bad API decisions in the admin into the generic views
just to get it done quicker.
--
Ticket URL: <https://code.djangoproject.com/ticket/16256#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
g the
new behavior, that django.request loggings calls are fired in DEBUG=True,
too. We don't currently seem to have any direct tests for the logging
calls in Django, at least that I can find.)
--
Ticket URL: <https://code.djangoproject.com/ticket/16288#comment:2>
Django <https://code.djangop
ion: => fixed
Comment:
In [16429]:
{{{
#!CommitTicketReference repository="" revision="16429"
Fixed #16076 -- Updated Hungarian l10n formats. Thanks, slink.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16076#comment:6>
Django <https://code.dj
jangoproject.com/ticket/15943#comment:4>
Django <https://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 email to djan
,
}
}}}
This will allow the filter to be used in more places, e.g. you could use a
more complex settings-time condition.
Regards,
Vinay Sajip
--
Ticket URL: <https://code.djangoproject.com/ticket/16288#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for pe
ton api right. Installed the pep8 checker in sublime
after the last changes so that should be fixed next time too.
--
Ticket URL: <https://code.djangoproject.com/ticket/16213#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
-
#16206: DB router example causes bug in django admin delete
--+---
Reporter: foxwhisper | Owner: nobody
Type: Bug | Status: closed
Milestone
and opens
up possibilities to override/extend behaviour.
--
Ticket URL: <https://code.djangoproject.com/ticket/16289>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the G
icket URL: <https://code.djangoproject.com/ticket/16289#comment:1>
Django <https://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 t
rkaround I did, was to force django to evaluate the first query,
and then use the result as input for the next. Maybe this should be the
default, since MySQL doesn't support the action. Or atleast Django should
explain the solution of forcing evaluating, and the slowdowns, that might
have
>
> objects = Model.objects.filter(key=value).values_list('id',
> flat=True)[:4]
> Model.objects.filter(id!__in=objects)
>
> Of course this example makes no sense.
> But the workaround I did, was to force django to evaluate the first
> query, and then use the result as input f
ould like that.
This is related to #10403 but applies to all !FormSets, not just
!ModelFormSets. Marking as duplicate with a note in the other ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/16289#comment:2>
Django <https://code.djangoproject.com/>
The Web framewo
.com/ticket/10403#comment:3>
Django <https://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 email to django-updates@go
):
* needs_better_patch: 0 => 1
Comment:
Looks okay to me, but it needs appropriate rst markup (backticks around
!ValueError is all that I see missing.)
--
Ticket URL: <https://code.djangoproject.com/ticket/16168#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for
RL: <https://code.djangoproject.com/ticket/16239#comment:4>
Django <https://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 email to
UI/UX: 0 |
+--
Comment (by melinath):
Looks fine to me, but I'd feel strange RFCing it since I accepted it.
--
Ticket URL: <https://code.djangoproject.com/ticket/16262#comment:5>
Django
Comment:
as #15805 is fixed, can this be checked in?
--
Ticket URL: <https://code.djangoproject.com/ticket/14608#comment:32>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the G
resses the
problem at the source.
> (Also, I'm wondering if this patch ought to come with a test verifying
the new behavior, that django.request loggings calls are fired in
DEBUG=True, too. We don't currently seem to have any direct tests for the
logging calls in Django, at least that I can find
an eye on it ;)
--
Ticket URL: <https://code.djangoproject.com/ticket/14608#comment:33>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django update
field
My personal feeling would be to send all values through coerce, but I
suppose the alternative would be to simply document this behavior more
explicitly.
--
Ticket URL: <https://code.djangoproject.com/ticket/16291>
Django <https://code.djangoproject.com/>
The Web framew
goproject.com/ticket/16239#comment:5>
Django <https://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 email to
later on.
--
Ticket URL: <https://code.djangoproject.com/ticket/10403#comment:4>
Django <https://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.
=> Ready for checkin
Comment:
That looks great, thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/13956#comment:19>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribe
this when extending the helper tags.
--
Ticket URL: <https://code.djangoproject.com/ticket/13956#comment:20>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Gro
;https://code.djangoproject.com/ticket/13956#comment:21>
Django <https://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, sen
list about it,
too.
--
Ticket URL: <https://code.djangoproject.com/ticket/13956#comment:22>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django update
In https://docs.djangoproject.com/en/1.3/ref/contrib/localflavor
/#switzerland-ch the link to http://adi.kousz.ch/artikel/IDCHE.htm isn't
working.
--
Ticket URL: <https://code.djangoproject.com/ticket/16292>
Django <https://code.djangoproject.com/>
The Web framework for perfect
0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I couldn't find another page containing that information, so I agree that
we should just remove the link.
--
Ticket URL: <https://code.djangoproject.com/ticket/16292#comment:1>
Django <https://code.django
d => Ready for checkin
Comment:
Patch is OK.
--
Ticket URL: <https://code.djangoproject.com/ticket/16292#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to t
=> closed
* resolution: => fixed
Comment:
In [16435]:
{{{
#!CommitTicketReference repository="" revision="16435"
Fixed #16292 -- Removed broken link for Swiss localflavor documentation.
Thanks, BernhardEssl.
}}}
--
Ticket URL: <https://code.djangoproject.co
In [16436]:
{{{
#!CommitTicketReference repository="" revision="16436"
[1.3.X] Fixed #16292 -- Removed broken link for Swiss localflavor
documentation. Thanks, BernhardEssl.
Backport from trunk (r16435).
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16292#comment:4>
Dj
use.
--
Ticket URL: <https://code.djangoproject.com/ticket/14757#comment:6>
Django <https://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
:
fixed the doctype in 5704-r16435.diff
--
Ticket URL: <https://code.djangoproject.com/ticket/5704#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Djan
github.com/trapeze/fancy_tag
Let me know if you'd like me to submit this as a patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/13956#comment:23>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message beca
to be maintained?
And if so, to what extent.
--
Ticket URL: <https://code.djangoproject.com/ticket/16174#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the G
1 - 100 of 204036 matches
Mail list logo
