Super ... thanks Malcolm!
I'll start later today.
-Sandy
PS> Congratulations ... looks like a great addition.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send emai
On Wed, 2007-06-13 at 23:05 +1000, Malcolm Tredinnick wrote:
> On Wed, 2007-06-13 at 05:50 -0700, ZebZiggle wrote:
[...]
> >
> > 3. I've read http://code.djangoproject.com/wiki/UnicodeBranch but are
> > there any more docs/examples of the conversion process available.
>
> Read the UnicodeBranch
On Wed, 2007-06-13 at 05:50 -0700, ZebZiggle wrote:
> Hi, I'm really stuck on a bug (decode exceptions on attempting to save
> utf-8 to postgres text fields) and suspect I'm going to need the
> unicode branch to solve it. But I have some questions:
>
> 1. When is it likely that this branch will b
Hi, I'm really stuck on a bug (decode exceptions on attempting to save
utf-8 to postgres text fields) and suspect I'm going to need the
unicode branch to solve it. But I have some questions:
1. When is it likely that this branch will be merged with trunk?
2. How would you rank the stability of t
On Sun, 2007-06-03 at 13:39 +1000, Malcolm Tredinnick wrote:
> Hi Eugene,
>
> On Sat, 2007-06-02 at 21:46 +, Eugene Morozov wrote:
[...]
> > I've checked out unicode branch today and immediately found two bugs.
> > This code doesn't work:
> > def __unicode__(self):
> > langs = dic
Hi Eugene,
On Sat, 2007-06-02 at 21:46 +, Eugene Morozov wrote:
>
>
> On 24, 17:06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > Hi folks,
> >
> > The unicode branch, [1], is now at a point where it is essentially
> > feature-complete and could do with a bit of heavy testing from t
On 24, 17:06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> The unicode branch, [1], is now at a point where it is essentially
> feature-complete and could do with a bit of heavy testing from the wider
> community.
>
> So if you have some applications that work against Django
Hi Malcolm!
On Sat, May 26, Malcolm Tredinnick wrote:
> On Fri, 2007-05-25 at 17:17 +0200, Michael Radziej wrote:
> > First, I found that I have a problem with commit 5255 together with the test
> > client. It breaks loading the modules, probably due to recursive imports.
> >
> > - management ac
On May 24, 2:06 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> The unicode branch, [1], is now at a point where it is essentially
> feature-complete and could do with a bit of heavy testing from the wider
> community.
>
> So if you have some applications that work against Django's current
>
On May 30, 3:09 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Everything is ready (you can see all the pieces that were ported over in
> the "TODO" list on the UnicdeBranch wiki page). Syndication has
> definitely been tested with non-ASCII content, so it should also work.
> Any failures a
On Tue, 2007-05-29 at 08:38 -0700, Almad wrote:
> Hi,
>
> I'm trying to migrate to unicode branch, but Syndication framework
> won't work for me (usual UnicodeDecodeError). I made sure that all
> strings are u'' ones.
>
> Is this middleware ready for unicode?
Everything is ready (you can see al
Hi,
I'm trying to migrate to unicode branch, but Syndication framework
won't work for me (usual UnicodeDecodeError). I made sure that all
strings are u'' ones.
Is this middleware ready for unicode?
Thank You,
Almad
--~--~-~--~~~---~--~~
You received this messa
On Mon, 2007-05-28 at 22:02 +1000, Malcolm Tredinnick wrote:
> On Mon, 2007-05-28 at 13:55 +0200, Michal wrote:
> [...]
> >
> > You are right, the problem is in the database.
> >
> > It seems like the test database is created in SQL_ASCII encoding. I
> > looked into psql terminal and found:
> >
Malcolm Tredinnick wrote:
> There are now TEST_DATABASE_CHARSET and TEST_DATABASE_COLLATION (the
> latter for MySQL only) settings. These are [5380] for trunk and [5381]
> in the unicode branch.
>
> I've tested it in as far as seeing that the test databases are created
> with the right encodings
Oh man... look like we are not going to file any tickets to
code.djangoproject.com... I should feel sorry for that because I was
one of them ;-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
El mar, 29-05-2007 a las 20:22 +1000, Malcolm Tredinnick escribió:
> Fixed in [5378].
Thanks, it works perfectly now! ;)
> It's actually a good bug to find; we were violating the WSGI spec, so it
> actually was an error in our wsgi handler. Fortunately, the dev server
> is very aggressive about
On Tue, 2007-05-29 at 20:03 +1000, Malcolm Tredinnick wrote:
[...]
>
> If anybody doesn't believe software development is hard, this is a
> beautiful example. I fixed a very similar problem for modpython last
> night. At the same time I looked for analogous problems in the other
> handlers and di
El mar, 29-05-2007 a las 20:03 +1000, Malcolm Tredinnick escribió:
> There are no bugs on the unicode branch; so it's clearly your fault. :-)
Ahh! I knew I knew... :)
> However, just this once, we can adjust the code so that this doesn't
> happen.
Oh, thanks!!! :)
> If anybody doesn't believe so
On Tue, 2007-05-29 at 11:58 +0200, Marc Fargas wrote:
> Hi there,
> When using i18n I'm getting a nice stacktrace for every request, this
> only happens once you set the language for a client and the exception
> raises due to Content-Language being a Unicode string for some reason.
>
> Backtrace:
Hi there,
When using i18n I'm getting a nice stacktrace for every request, this
only happens once you set the language for a client and the exception
raises due to Content-Language being a Unicode string for some reason.
Backtrace:
Traceback (most recent call last):
File
On Tue, 2007-05-29 at 09:27 +0200, Sandro Dentella wrote:
> > > Do we need such a settings or we really need to *copy* database encoding
> > > so
> > > that tests are done exactly as the application database. (if it's possible
> > > to use other than utf8...).
> >
> > That assumes there is an ap
> > Do we need such a settings or we really need to *copy* database encoding so
> > that tests are done exactly as the application database. (if it's possible
> > to use other than utf8...).
>
> That assumes there is an application database to copy and/or that is
> configured sensibly. It's a bit
On Tue, 2007-05-29 at 00:30 +0200, Sandro Dentella wrote:
> On Mon, May 28, 2007 at 04:26:17PM -0500, Jeremy Dunck wrote:
> >
> > On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > > Okay... time to fix that problem then. Probably need to introduce a
> > > settings for tests only for d
On Mon, 2007-05-28 at 16:26 -0500, Jeremy Dunck wrote:
> On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > Okay... time to fix that problem then. Probably need to introduce a
> > settings for tests only for database encoding. I should have done that
> > when I first saw the problem ins
On Mon, May 28, 2007 at 04:26:17PM -0500, Jeremy Dunck wrote:
>
> On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > Okay... time to fix that problem then. Probably need to introduce a
> > settings for tests only for database encoding. I should have done that
> > when I first saw the p
On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Okay... time to fix that problem then. Probably need to introduce a
> settings for tests only for database encoding. I should have done that
> when I first saw the problem instead of trying to dodge around it.
FWIW, as a workaround, in M
>> Aaah! :-(
>>
>> I've been fighting this problem a bit when testing with MySQL, too,
>> because my system creates the databases in LATIN1 if I don't tell it
>> anything special and so the test database can't hold the full unicode
>> range of characters. It creates PostgreSQL database in UTF-8 on
Thanks for fixing that.
I also find using the smart_str() really handy, for cases where stuff
getting out of python.
Regards,
itsnotvalid
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To p
Am 28.05.2007 um 15:51 schrieb Malcolm Tredinnick:
> I can't replicate this problem, but I can take a guess at what is
> going
> on. In [5377] I've checked in what is probably a fix for the problem.
> Could you try it and see if it changes things for you?
Looks good so far. I'll report if the
On Mon, 2007-05-28 at 11:27 +0200, Andreas Ahlenstorf wrote:
> Hi,
>
> I'm having issues with the Unicode Branch and mod_python (the
> development server ist working fine). That's what's comming from
> mod_python:
>
> Phase: 'PythonHandler'
> Handler:'django.core.handlers.mo
Malcolm Tredinnick wrote:
> On Mon, 2007-05-28 at 13:55 +0200, Michal wrote:
> [...]
>> You are right, the problem is in the database.
>>
>> It seems like the test database is created in SQL_ASCII encoding. I
>> looked into psql terminal and found:
>>
>> List of databases
>>N
On Mon, 2007-05-28 at 13:55 +0200, Michal wrote:
[...]
>
> You are right, the problem is in the database.
>
> It seems like the test database is created in SQL_ASCII encoding. I
> looked into psql terminal and found:
>
> List of databases
>Name | Owner| Encodin
On Sun, 2007-05-27 at 13:34 -0700, itsnotvalid wrote:
> I got an error when I am using admin interface to submit some forms as
> following the Django book (CH6).
>
> When the form in admin interface saving.
[... snip...]
>
> UnicodeDecodeError at /admin/books/author/add/
> 'ascii' codec can'
Malcolm Tredinnick wrote:
> On Mon, 2007-05-28 at 13:16 +0200, Michal wrote:
>> Malcolm Tredinnick wrote:
>>> On Mon, 2007-05-28 at 12:59 +0200, Michal wrote:
>>> [...]
My note was in relation with latest error (ie. I have problem with
execution of tests due to verbose_name error).
On Mon, 2007-05-28 at 13:16 +0200, Michal wrote:
> Malcolm Tredinnick wrote:
> > On Mon, 2007-05-28 at 12:59 +0200, Michal wrote:
> > [...]
> >> My note was in relation with latest error (ie. I have problem with
> >> execution of tests due to verbose_name error).
> >>
> >> I am just after dinner
Malcolm Tredinnick wrote:
> On Mon, 2007-05-28 at 12:59 +0200, Michal wrote:
> [...]
>> My note was in relation with latest error (ie. I have problem with
>> execution of tests due to verbose_name error).
>>
>> I am just after dinner too, so I will try to find what is wrong in my
>> application.
On Mon, 2007-05-28 at 12:59 +0200, Michal wrote:
[...]
>
> My note was in relation with latest error (ie. I have problem with
> execution of tests due to verbose_name error).
>
> I am just after dinner too, so I will try to find what is wrong in my
> application... :)
>
>
> Once again, sorry
Malcolm Tredinnick wrote:
> On Mon, 2007-05-28 at 11:27 +0200, Michal wrote:
>> Malcolm Tredinnick wrote:
>>> On Mon, 2007-05-28 at 02:09 -0700, itsnotvalid wrote:
Michal, your error looks nearly identical to the one I encounter with
admin interface. Except the byte offending is not the
On Mon, 2007-05-28 at 11:27 +0200, Andreas Ahlenstorf wrote:
> Hi,
>
> I'm having issues with the Unicode Branch and mod_python (the
> development server ist working fine). That's what's comming from
> mod_python:
>
> Phase: 'PythonHandler'
> Handler:'django.core.handlers.mo
On Mon, 2007-05-28 at 11:27 +0200, Michal wrote:
> Malcolm Tredinnick wrote:
> > On Mon, 2007-05-28 at 02:09 -0700, itsnotvalid wrote:
> >> Michal, your error looks nearly identical to the one I encounter with
> >> admin interface. Except the byte offending is not the same.
> >>
> >> I guess there
Malcolm Tredinnick wrote:
> On Mon, 2007-05-28 at 02:09 -0700, itsnotvalid wrote:
>> Michal, your error looks nearly identical to the one I encounter with
>> admin interface. Except the byte offending is not the same.
>>
>> I guess there is something between the model class and database
>> adapter
Hi,
I'm having issues with the Unicode Branch and mod_python (the
development server ist working fine). That's what's comming from
mod_python:
Phase: 'PythonHandler'
Handler:'django.core.handlers.modpython'
Traceback (most recent call last):
File "/usr/lib/python2.4/sit
On Mon, 2007-05-28 at 02:09 -0700, itsnotvalid wrote:
> Michal, your error looks nearly identical to the one I encounter with
> admin interface. Except the byte offending is not the same.
>
> I guess there is something between the model class and database
> adapters which adds those strange bytes
Michal, your error looks nearly identical to the one I encounter with
admin interface. Except the byte offending is not the same.
I guess there is something between the model class and database
adapters which adds those strange bytes.
--~--~-~--~~~---~--~~
You re
Hello Malcolm,
I try to make tests on my application, but after update of unicode
branch (now I am synced to revision 5371), I am unable to do it due to
some errors:
[EMAIL PROTECTED] app $./manage.py test staticpages
Creating test database...
Creating table auth_message
Creating table auth_gro
On Sun, 2007-05-27 at 13:34 -0700, itsnotvalid wrote:
> I got an error when I am using admin interface to submit some forms as
> following the Django book (CH6).
>
> When the form in admin interface saving.
> Traceback (most recent call last):
> File "F:\python25\Lib\site-packages\django-svn\unic
I got an error when I am using admin interface to submit some forms as
following the Django book (CH6).
When the form in admin interface saving.
Traceback (most recent call last):
File "F:\python25\Lib\site-packages\django-svn\unicode\django\core
\handlers\base.py" in get_response
77. response
On Fri, 2007-05-25 at 17:17 +0200, Michael Radziej wrote:
> Hi Malcolm,
>
> A short disclaimer: I'm currently trying the unicode branch with the
> autoescape patch and a
> couple of other patches, so my problems might really be my own problems,
> but I don't expect it.
>
>
> First, I found tha
On Fri, 2007-05-25 at 17:17 +0200, Michael Radziej wrote:
> Hi Malcolm,
>
> A short disclaimer: I'm currently trying the unicode branch with the
> autoescape patch and a
> couple of other patches, so my problems might really be my own problems,
> but I don't expect it.
>
>
> First, I found tha
Hi Malcolm,
A short disclaimer: I'm currently trying the unicode branch with the autoescape
patch and a
couple of other patches, so my problems might really be my own problems,
but I don't expect it.
First, I found that I have a problem with commit 5255 together with the test
client. It breaks
On Fri, 2007-05-25 at 09:20 +, Sam wrote:
> Most of the table mapping is taken from a GPL project.
>
> I've just emailed the authors to see if they would relicense the file
> to include it inside django.
>
> I'll update as soon as i have their replies.
Thanks. We only need the mapping table
Most of the table mapping is taken from a GPL project.
I've just emailed the authors to see if they would relicense the file
to include it inside django.
I'll update as soon as i have their replies.
On 25 mai, 10:44, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-05-25 at 10:31 +0
On Fri, 2007-05-25 at 10:31 +0200, David Larlet wrote:
> 2007/5/24, Malcolm Tredinnick <[EMAIL PROTECTED]>:
> >
> > Hi folks,
> >
> > The unicode branch, [1], is now at a point where it is essentially
> > feature-complete and could do with a bit of heavy testing from the wider
> > community.
>
>
> > File "/usr/lib/python2.4/urllib.py", line 1162, in urlencode
> > v = quote_plus(str(v))
> > UnicodeEncodeError: 'ascii' codec can't encode character u'\xf2' in
> > position 1: ordinal not in range(128)
>
> This should be fixed in [5338].
well... you already know it works like a charm!
2007/5/24, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> Hi folks,
>
> The unicode branch, [1], is now at a point where it is essentially
> feature-complete and could do with a bit of heavy testing from the wider
> community.
Thank you so much for this branch!
> Similarly, the slugify filter still
On Thu, 2007-05-24 at 09:13 -0700, sandro dentella wrote:
> Hi Malcom,
>
> I really welcome this branch and thank you all for the effort.
>
> Before I consider a bug what follows I'd ask if this should entitle
> me to use
> non ASCII letters in tests with test.client.
>
>I tried somet
On Thu, 2007-05-24 at 09:13 -0700, sandro dentella wrote:
> Hi Malcom,
>
> I really welcome this branch and thank you all for the effort.
>
> Before I consider a bug what follows I'd ask if this should entitle
> me to use
> non ASCII letters in tests with test.client.
>
>I tried somet
Malcolm Tredinnick wrote:
> The unicode branch, [1], is now at a point where it is essentially
> feature-complete and could do with a bit of heavy testing from the wider
> community.
Switched my site today to the branch. Works like a charm (translations,
admin, multilingual content).
--~--~
Thanks for your work! Definitely will test new branch soon & will tell
the results.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroup
Hi Malcom,
I really welcome this branch and thank you all for the effort.
Before I consider a bug what follows I'd ask if this should entitle
me to use
non ASCII letters in tests with test.client.
I tried something like self.client.get(url, dict(name=u'F\xf2')) to
get back
an error f
60 matches
Mail list logo
