My preference is for option 2: convert file system paths to unicode and use
unicode internally as much as possible. This is consistent with what we
have been doing/recommending for years, even if it is at odds with Python's
default for 2.X. See for example:
https://code.djangoproject.com/ticket/95
Hi Russell,
> I've had a look at the patches for (1) and (2), and to me, the look like
> mirror images of the same patch -- it's just a matter of whether we convert
> everything to bytes or unicode when we have the opportunity.
> My immediate reaction is that (2) -- keeping everything in unicod
On Sun, Dec 2, 2012 at 2:43 AM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> Hello,
>
> Django 1.5 beta 1 contains a regression for users who install Django or
> their projects under non-ASCII paths:
> https://code.djangoproject.com/ticket/19357 Unfortunately, the patch
> isn't
Le samedi 1 décembre 2012 19:43:12 UTC+1, Aymeric Augustin a écrit :
>
> Hello,
>
> Django 1.5 beta 1 contains a regression for users who install Django or
> their projects under non-ASCII paths:
> https://code.djangoproject.com/ticket/19357 Unfortunately, the patch
> isn't going to be trivial.
Hello,
Django 1.5 beta 1 contains a regression for users who install Django or their
projects under non-ASCII paths: https://code.djangoproject.com/ticket/19357
Unfortunately, the patch isn't going to be trivial. I'd like to have some
feedback before making changes.
In order to add compatibil
