Re: Trouble with internationalized path under windows

2012-01-23 Thread Chris Angelico
On Mon, Jan 23, 2012 at 12:49 PM, Rick Johnson wrote: > The fact is, Unicode is nothing more than a monkey patch for language > multiplicity. A multiplicity that is perpetuated on the masses due to > a blind adherence to the cult of xenophobia. I agree. We need to abolish all languages but one, a

Re: Trouble with internationalized path under windows

2012-01-22 Thread Rick Johnson
On Jan 22, 6:47 pm, Michael Torrie wrote: > I once argued to limit Python identifiers to latin letters only, but at > least that made some sort of sense (lowest-common denominator) and it > had nothing to do with running in an internationalized environment or > dealing with unicode or utf-8 -encod

Re: Trouble with internationalized path under windows

2012-01-22 Thread Benjamin Peterson
Jacob Hallén sotospeak.se> writes: > > I have a problem which ought to have an obvious solution, but I haven't found > one despite searching for many hours. The problem occurs on Windows. You may be running into the brokenness of the Python import system prior to 3.2. See http://bugs.python.or

Re: Trouble with internationalized path under windows

2012-01-22 Thread Michael Torrie
On 01/22/2012 01:52 PM, Rick Johnson wrote: > On Jan 22, 2:08 pm, Jacob Hallén wrote: > >> If I store these two files in say C:\Users\Admin\test everything works fine. >> >> If I store them in C:\Users\Admin\testф, I get an import error when running >> foo.py. The letter at the end of test is a

Re: Trouble with internationalized path under windows

2012-01-22 Thread Jacob Hallén
Sunday 22 January 2012 you wrote: > On Sun, Jan 22, 2012 at 12:08 PM, Jacob Hallén > > wrote: > > I have a problem which ought to have an obvious solution, but I haven't > > found one despite searching for many hours. The problem occurs on > > Windows. > > > > This is a version of my problem red

Re: Trouble with internationalized path under windows

2012-01-22 Thread Jacob Hallén
Sunday 22 January 2012 you wrote: > On Sun, Jan 22, 2012 at 12:08 PM, Jacob Hallén > > wrote: > > I have a problem which ought to have an obvious solution, but I haven't > > found one despite searching for many hours. The problem occurs on > > Windows. > > > > This is a version of my problem red

Re: Trouble with internationalized path under windows

2012-01-22 Thread Rick Johnson
On Jan 22, 2:08 pm, Jacob Hallén wrote: > If I store these two files  in say C:\Users\Admin\test everything works fine. > > If I store them in C:\Users\Admin\testф, I get an import error when running > foo.py. The letter at the end of test is a Russian "F", if it looks strange on > your terminal.

Re: Trouble with internationalized path under windows

2012-01-22 Thread Andrew Berg
On 1/22/2012 2:08 PM, Jacob Hallén wrote: > Am using WIndows 7 with a Swedish locale. The program uses Unicode > successfully internally, and the Windows help says that the locale only > applies to non-Unicode programs. I have tried with using characters from the > Latin-1 character set in the p

Re: Trouble with internationalized path under windows

2012-01-22 Thread Chris Rebert
On Sun, Jan 22, 2012 at 12:08 PM, Jacob Hallén wrote: > I have a problem which ought to have an obvious solution, but I haven't found > one despite searching for many hours. The problem occurs on Windows. > > This is a version of my problem reduced to its essentials: > > I have a file foo.py:: > >

Trouble with internationalized path under windows

2012-01-22 Thread Jacob Hallén
I have a problem which ought to have an obvious solution, but I haven't found one despite searching for many hours. The problem occurs on Windows. This is a version of my problem reduced to its essentials: I have a file foo.py:: import bar and a file bar.py : baz = 42 If I store these two fi