(complete version follows)
Hello,
I'm looking for some feedback on #19468 before making a decision. It's one
of the tickets that currently block the 1.5 release.
Here's a summary of the problem.
Django must decode environ['PATH_INFO'] to obtain request.path, where
decoding means :
1 - URL-dec
The validation documentation for forms says that to_python on the form
field is the first step in validation. I've written some code (the details
of which don't really matter) which makes use of to_python on fields in
doing so I discovered that "to_python" on ModelMultipleChoiceField doesn't
wo
On 18 December 2012 09:34, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> (complete version follows)
>
> Hello,
>
> I'm looking for some feedback on #19468 before making a decision. It's one
> of the tickets that currently block the 1.5 release.
>
> Here's a summary of the problem
On Monday, 2 June 2008 02:45:07 UTC+2, Ludvig Ericson wrote:
>
> I'd rather see this be leaved as-is, since I haven't seen a single
>
> report on these broken pipe 'issues'.
>
Here's a report:
I'm using PhantomJS (headless webkit browser) to test for javascript errors
on my site. Using the Live
On Tue, Dec 18, 2012 at 3:34 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
>
> Currently, Django uses utf-8. As far as I can tell, that's more a
> side-effect of (ab)using force_str than anything else. It also has the
> drawback of making it impossible to serve perfectly legit
2012/12/18 Karen Tracey
> https://code.djangoproject.com/ticket/5738
>
> Comment #10 notes that utf-8 is what Django will use but with the last fix
> noted against that ticket it is easier for the request class to be
> subclassed to change things for an installation where a different charset
> fo
On Wed, Dec 12, 2012 at 3:56 PM, Michael Elsdörfer wrote:
> $ pip install django==1.1
If you mean "The most recent point release in the 1.1 family", then
that is "Django>1.1,<1.2"*.
If you mean 1.1.1, then that is "Django==1.1.1"
Cheers
Tom
* If you are using pypi, then "Django<1.2" will do th
2012/12/18 Łukasz Rekucki
>
> I wonder if UTF-8 with "surrogates escape" error mode makes sense here.
> Python 3 uses it for decoding file-system paths, where it's not always
> possible to determine the charset. I think it's pretty much the same case.
> After all, the %-coded bytes can be some b
On Dec 18, 2012, at 5:18 AM, Emil Stenström wrote:
> On Monday, 2 June 2008 02:45:07 UTC+2, Ludvig Ericson wrote:
> I'd rather see this be leaved as-is, since I haven't seen a single
> report on these broken pipe 'issues'.
>
> Here's a report:
>
> I'm using PhantomJS (headless webkit browser)
Ok, then, what about SlugField?
Is not the same case?
Regards.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/FQMFohktYdsJ.
To post to this grou
Hi,
First post here. I'm extremely new to Django and I have been fumbling my
way through the DjangoProject "poll" app tutorial for a couple weeks now. I
understand a lot of what's going on, but a lot of things are completely
lost on me as well. That said, I'm to the point of actually using the
Please ask questions about using Django on django-users. The topic of this
list is the development of Django itself.
Thanks,
Karen
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googl
Sorry, Karen. Thanks for the reply. I'll head over there!
On Tuesday, December 18, 2012 10:34:27 PM UTC-5, Karen Tracey wrote:
>
> Please ask questions about using Django on django-users. The topic of this
> list is the development of Django itself.
>
> Thanks,
> Karen
>
--
You received this me
13 matches
Mail list logo
