On 5 Jul 2006, at 15:21, Jacob Kaplan-Moss wrote:
> Er, no -- that PEP was actually rejected. My impression is that the
> str/unicode distinction won't be eliminated until Py3k.
Guido's keynote at EuroPython confirmed that - one of the big changes
in Py3K (which is now planned for an initial
Jacob Kaplan-Moss wrote:
> On Jul 5, 2006, at 9:05 AM, Filipe wrote:
> > and the first changes towards that will start appearing in python 2.5:
> > http://www.python.org/dev/peps/pep-0332/
>
> Er, no -- that PEP was actually rejected. My impression is that the
> str/unicode distinction won't be
On 7/5/06, Filipe <[EMAIL PROTECTED]> wrote:
> and the first changes towards that will start appearing in python 2.5:
> http://www.python.org/dev/peps/pep-0332/
That's rejected, so not actually in 2.5, right?
--~--~-~--~~~---~--~~
You received this message because
On Jul 5, 2006, at 9:05 AM, Filipe wrote:
> and the first changes towards that will start appearing in python 2.5:
> http://www.python.org/dev/peps/pep-0332/
Er, no -- that PEP was actually rejected. My impression is that the
str/unicode distinction won't be eliminated until Py3k.
Jacob
--~-
Andrey Golovizin wrote:
> Jacob Kaplan-Moss wrote:
> > "... with too many backwards-incompatible changes ..." -- as Hugo
> > points out, this will break a lot of existing code.
> Well, some day Django will have to switch to unicode anyway (even Python-3000
> is going to use unicode strings everywh
Bjørn Stabell wrote:
> What if the patch required everything to be Unicode, meaning:
>
> * all programmers would have to become aware of Unicode to some extent
> * all code would suffer the (minior) performance penalty of encoding
> and decoding all text
The second point is arguable. Currently
Jacob Kaplan-Moss wrote:
> On Jun 28, 2006, at 8:08 AM, Gábor Farkas wrote:
> > let's imagine for a second that the unicode-django patch is done and
> > available (it's not, but let's imagine it is)
> >
> > would there be a chance to get it applied?
>
> Obviously that would depend on the quality o
Jacob Kaplan-Moss wrote:
> On Jun 28, 2006, at 6:07 AM, Gábor Farkas wrote:
>> what i think we are missing the most is to hear about the "main"
>> developers (project owners?) (adrian, malcolm, jacob etc.) opinion
>> about
>> unicode-ification. if they think we should switch django completely to
Hi,
> I think we should do this.
>
> We are, after all, perfectionists.
>
> Not only do we want to show even more love toward the international
> community, I just like the idea of passing Unicode strings everywhere.
> It seems so clean.
I whole-heartedly agree! It's just much cleaner and actual
Hi all, longtime listener, first time caller...
We're learning Django now and hope to use it for next gen online surveys
later this year. We're doing an 8-language app now in Unicode in Active
Server Pages and while so far it hasn't been as painful as I'd expected,
I'd be even more drawn to Dj
On 28 Jun 2006, at 15:32, Adrian Holovaty wrote:
> The only big problem I see is that it could confuse the (unfortunately
> large) mass of programmers who don't understand Unicode yet. That is a
> big potential pitfall.
That's very true. The documentation overhead will be considerable. It
shou
On 6/28/06, Andrey Golovizin <[EMAIL PROTECTED]> wrote:
> I am using Django for about half a year and it rocks. Indeed, it would rock
> even more if it switched from using UTF-8 bytestrings to use unicode strings
> everywhere.
Some quick thoughts --
I think we should do this.
We are, after all,
On Jun 28, 2006, at 9:03 AM, Simon Willison wrote:
> As far as engineering goes, developing a water-tight test suite seems
> like a critical component for confidently adding unicode support.
I couldn't agree more strongly.
Sucks that writing good tests is so damn hard :)
Jacob
--~--~-~
On Jun 28, 2006, at 8:08 AM, Gábor Farkas wrote:
> let's imagine for a second that the unicode-django patch is done and
> available (it's not, but let's imagine it is)
>
> would there be a chance to get it applied?
Obviously that would depend on the quality of the patch and the
ramifications of
On 28 Jun 2006, at 14:43, Andrey Golovizin wrote:
> Unicode awareness may seem not a big issue for English-speakers
> (for whom
> plain ASCII is perfectly enough :)), but for others (like me) it's
> of crucial
> importance.
I don't think that's true. On today's Web there's no guarantee at al
Jacob Kaplan-Moss wrote:
> "... with too many backwards-incompatible changes ..." -- as Hugo
> points out, this will break a lot of existing code.
Well, some day Django will have to switch to unicode anyway (even Python-3000
is going to use unicode strings everywhere). Right now is a good time f
Gábor Farkas wrote:
> Jacob Kaplan-Moss wrote:
>>
>> So I think -- for now -- there are more important places to spend our
>> energy.
>
>
> 2. 'to spend our energy'. i think it's a little more complicated. if
> someone is willing to help-with/work-on django-unicode, it does not mean
> that ot
Jacob Kaplan-Moss wrote:
> On Jun 28, 2006, at 6:07 AM, Gábor Farkas wrote:
>> what i think we are missing the most is to hear about the "main"
>> developers (project owners?) (adrian, malcolm, jacob etc.) opinion
>> about
>> unicode-ification. if they think we should switch django completely to
Jacob Kaplan-Moss wrote:
> Just one
> example is the issue of template encodings -- do we need to start
> indicating that a certain template is UTF-8 or whatever?
May be I don't understand what do you mean... But this problem is not
related to internals being in unicode or not. Most templat
On Jun 28, 2006, at 6:07 AM, Gábor Farkas wrote:
> what i think we are missing the most is to hear about the "main"
> developers (project owners?) (adrian, malcolm, jacob etc.) opinion
> about
> unicode-ification. if they think we should switch django completely to
> unicode, then fine. but if t
hugo wrote:
> Hi,
>
>> So, what's stopping Django from switching to unicode? Is someone working on
>> it? And finally, what should I do to see my sweet Django fully
>> unicode-aware? :)
>
> Well, as a start, take a look at the impact analysis page at
> http://code.djangoproject.com/wiki/UnicodeI
Hi,
> So, what's stopping Django from switching to unicode? Is someone working on
> it? And finally, what should I do to see my sweet Django fully
> unicode-aware? :)
Well, as a start, take a look at the impact analysis page at
http://code.djangoproject.com/wiki/UnicodeInDjango and contribute
up
Hi,
I am using Django for about half a year and it rocks. Indeed, it would rock
even more if it switched from using UTF-8 bytestrings to use unicode strings
everywhere.
The main drawbacks of using UTF-8 strings are:
- regexps won't work on utf-8 bytestrings containing non-ASCII characters;
- l
23 matches
Mail list logo
