I find it really disturbing for someone that comes for the first time and *thinks* that's it's possible (especially when it was possible in 1.0, and you'll get a lot of references on the web on 'tips' and similar usage) to access the filenames in a pre_save signal.
The problem is that *if* you don't know that it's impossible now, you'll try to access instance.myattribute.path (which contained the correct path to the file in Django 1.0) and get a result, but a wrong one! Isn't it possible to prevent access to the attribute or at least set it to something that will not be interpreted as "strange"? On May 13, 7:18 am, Armin Ronacher <armin.ronac...@active-4.com> wrote: > Hi, > > On 13 Mai, 00:42, Yuri Baburov <burc...@gmail.com> wrote:> Also on OS X you > can set if filename is case-sensitive on per-volume > > basis, when formatting, and usually it's case-insensitive. windows is > > always case insensitive, linux is usually case-sensitive. > > I'm not talking about case sensitivity here but unicode normalization > which is controlled in the IO system. For example if you're creating a > file öäü.txt (\x94\x84\x81) OS X will store it as o\u0308a\u0308u > \u0308.txt on the filesystem. No matter if the filesystem is HSF, NFS, > a mounted samba share or anything else. On Linux the filesystem might > have an encoding but is generally non unicode-aware and no > normalization takes place at all. This could lead to weird effects > where you have \x94\x84\x81.txt in the database but o\u0308a\u0308u > \u0308.txt on the filesystem which obviously makes it impossible to > move the data from an OS X system to a linux one or access an NFS > share from two systems at the same time. > > > This does matter when one filename has the same letters as another but > > some letters have different case. This also can cause troubles when > > moving existing DB and files from one filesystem to another. > > I'm well aware of that, but that's a different story. > > Regards, > Armin --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
