Django developers Google Group

Re: A (last-minute) compromise on {% url %}

bennyd...@gmail.com (daonb) — Sat, 30 Aug 2008 15:50:12 UT

+1 for a sweet feature.

Re: Working on comments

chris.moff...@gmail.com (chris.moffitt@gmail.com) — Sat, 30 Aug 2008 14:48:33 UT

Hey Bruce,

Reading between the lines, I think you meant to post this in Satchmo-
dev ;) Nonetheless, this is good news!

-Chris

Re: Does CharField still required max_length? Or is it a bug?

kmtra...@gmail.com (Karen Tracey) — Sat, 30 Aug 2008 12:40:33 UT

I don't believe this is correct. A CharField needs a max_length parameter
to pass validation. You may not need it for issuing test queries, etc. in a
manage.py shell, but it is still needed in general, as documented:
[link]
Karen
p.s. This conversation really belongs on django-users, please follow up

Re: Does CharField still required max_length? Or is it a bug?

mnis4...@gmail.com (M N Islam Shihan) — Sat, 30 Aug 2008 04:56:39 UT

Yes, it has been made optional with this syntax class CharField(*
max_length=None*[, ***options*])
This is true for all other model fields as well that were expecting
max_length parameter.
Regards,
Shihan

Working on comments

bkro...@gmail.com (Bruce Kroeze) — Sat, 30 Aug 2008 06:40:39 UT

I'm mostly through with a drop-in replacement for the old comments, using
the new Comment system and signals. It should be slick.
When it tests out, I'll also commit the new save() parameters mentioned in
the backwards-incompatible page, and we should be again compatible with the
latest Django trunk.

Does CharField still required max_length? Or is it a bug?

gonef...@gmail.com (guoqiang qian) — Sat, 30 Aug 2008 04:49:20 UT

hi,all
I use django beta2 and find that model's charfield doesn't require
max_length parameter anymore. Is there any thing wrong?

Re: 500 error if django run in scgi mode(fcgi is ok)

mar...@diers.us (Martin Diers) — Fri, 29 Aug 2008 20:33:53 UT

If you want a response, you will need to ask this on the django-users
list. This list is for the discussion of developing the Django
framework itself.

Re: A (last-minute) compromise on {% url %}

jan...@leidel.info (Jannis Leidel) — Fri, 29 Aug 2008 19:07:35 UT

Am 29.08.2008 um 17:18 schrieb Jacob Kaplan-Moss:
Hell, no! That's perfect and also works with blocktrans.
..and let's us kill that captureas in Pinax, yay!
Cheers,
Jannis

Re: queryset set difference

malc...@pointy-stick.com (Malcolm Tredinnick) — Fri, 29 Aug 2008 18:02:56 UT

And because I wasn't concentrating about which list I was reading, here
comes the obligatory statement:
Please take any follow-ups to django-users. This mailing list is
for the internal development of Django itself. "How to use"
questions should go to the django-users mailing list.

Re: queryset set difference

malc...@pointy-stick.com (Malcolm Tredinnick) — Fri, 29 Aug 2008 18:00:37 UT

If they already exist as querysets, the set difference is the way to go.
There's probably no need to turn it back into a list at the end, since
Python's sets are iterable containers. It depends what you want to do
with it afterwards.
However, if you know the filters you are applying, you can get the

queryset set difference

cekan...@gmail.com (ryan) — Fri, 29 Aug 2008 17:51:29 UT

I have 2 querysets q1 and q2.

I want q3 = q2-q1, where q3 is a queryset object and contains only the
objects in q2 that are not in q1.

Is there built in support for this operation?

The only thing I can think to do is:
list( set(q2) - set(q1) )
It doesn't return a queryset, but I can deal with it if there's no

Re: A (last-minute) compromise on {% url %}

eduardo.pad...@gmail.com (Eduardo O. Padoan) — Fri, 29 Aug 2008 15:53:28 UT

+1 -- Pinax could deprecate {% captureas %} with this feature. Seems
like a non-intentional pro :)

Re: A (last-minute) compromise on {% url %}

lar...@gmail.com (David Larlet) — Fri, 29 Aug 2008 15:43:48 UT

Le 29 août 08 à 17:18, Jacob Kaplan-Moss a écrit :
+1 for this, before I test if someone already knows the answer, is it
possible to use this var in blocktrans?
{% url args as myurl %}
{% blocktrans %}
foo <a href="{{ myurl }}">baz</a>
{% endblocktrans %}
That's potentially the best solution for the endless discussion about

A (last-minute) compromise on {% url %}

jacob.kaplanm...@gmail.com (Jacob Kaplan-Moss) — Fri, 29 Aug 2008 15:18:49 UT

Hi folks --
While working on some URL-related issues, I ran across a pretty big
problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into
the templates: if it does that, there's no way to have "optional"
links. The perfect example is #7810 and the admin docs: if the URLs
for the admin doc views are installed, the admin should show a

Re: Recover/Reset password on code.djangoproject.com

jacob.kaplanm...@gmail.com (Jacob Kaplan-Moss) — Fri, 29 Aug 2008 14:16:55 UT

[link]
Jacob