Re: [Python-Dev] Import and unicode: part two

On Fri, Jan 21, 2011 at 4:44 PM, Atsuo Ishimoto wrote: > On Fri, Jan 21, 2011 at 2:59 PM, Nick Coghlan wrote: >> >> These all sound like good reasons to continue to *advise* against >> using non-ASCII module names. But aside from that, they sound exactly >> like a lot of the arguments we heard wh

Re: [Python-Dev] r88121 - python/branches/py3k/Doc/whatsnew/3.2.rst

Am 20.01.2011 10:04, schrieb raymond.hettinger: > +os > +-- > + > +Different operating systems use various encodings for filenames and > environment > +variables. The :mod:`os` module provides two new functions, > +:func:`~os.fsencode` and :func:`~os.fsdecode`, for encoding and decoding > +filen

Re: [Python-Dev] Import and unicode: part two

On 1/20/2011 12:44 PM, Toshio Kuratomi wrote: The problem occurs in that the code that one of the parties develops (either the students or the professors) is developed on one of those OS's and then used on the other OS. The problem that I reported and hope will be fixed is that private code w

Re: [Python-Dev] Import and unicode: part two

On Fri, Jan 21, 2011 at 3:44 PM, Atsuo Ishimoto wrote: > I don't want Python to encourage people to use non-ascii module names. > Today, seeing UnicodeEncodingError is one of popular reasons for > newbies to abandon learning Python in Japan. Non-ascii module name is > an another source of confusio

Re: [Python-Dev] Import and unicode: part two

On Jan 20, 2011, at 3:55 PM, Antoine Pitrou wrote: > On Thu, 20 Jan 2011 15:27:08 -0500 > Glyph Lefkowitz wrote: >> >> To support the latter, could we just make sure that zipimport has a >> consistent, >> non-locale-or-operating-system-dependent interpretation of encoding? > > It already has,

Re: [Python-Dev] [Python-checkins] r87815 - peps/trunk/pep-3333.txt

On Jan 20, 2011, at 9:31 PM, Ezio Melotti wrote: >> Modified: peps/trunk/pep-.txt >> == >> --- peps/trunk/pep-.txt (original) >> +++ peps/trunk/pep-.txt Fri Jan 7 16:39:27 2011 >> @@ -310,9 +310,9 @@ >

Re: [Python-Dev] [Python-checkins] r87815 - peps/trunk/pep-3333.txt

On Fri, Jan 7, 2011 at 4:39 PM, phillip.eby wrote: > Author: phillip.eby > Date: Fri Jan 7 16:39:27 2011 > New Revision: 87815 > > Log: > More bytes I/O fixes > > > Modified: > peps/trunk/pep-.txt > > Modified: peps/trunk/pep-.txt > >

Re: [Python-Dev] [Python-checkins] devguide: Copy over the dev FAQ and *only* strip out stuff covered elsewhere in the

On Fri, Jan 21, 2011 at 6:42 AM, brett.cannon wrote: > brett.cannon pushed 82d3a1b694b3 to devguide: > > http://hg.python.org/devguide/rev/82d3a1b694b3 > changeset:   167:82d3a1b694b3 > user:        Brett Cannon > date:        Thu Jan 20 12:40:47 2011 -0800 > summary: >  Copy over the dev FAQ and

Re: [Python-Dev] Import and unicode: part two

On Fri, Jan 21, 2011 at 5:27 AM, Toshio Kuratomi wrote: > I think that both ideas are inferior to mandating that every python module > filename is ascii.  From what I'm getting from Victor's posts is that he, at > least, considers the portability problems to be ignorable because dealing > with amb

Re: [Python-Dev] Import and unicode: part two

Am 20.01.2011 12:51, schrieb Victor Stinner: > You only give theorical arguments Read Anathem lately? ;) Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/ma

Re: [Python-Dev] [Python-checkins] r88127 - in python/branches/py3k/Misc: README.AIX README.OpenBSD cheatsheet

On Thu, Jan 20, 2011 at 13:09, Alexander Belopolsky wrote: > On Thu, Jan 20, 2011 at 3:37 PM, Brett Cannon wrote: >> On Thu, Jan 20, 2011 at 12:09, M.-A. Lemburg wrote: > ..    python/branches/py3k/Misc/cheatsheet >>> >>> Wouldn't it be better to update this useful file (as part of your >>>

Re: [Python-Dev] [Python-checkins] r88127 - in python/branches/py3k/Misc: README.AIX README.OpenBSD cheatsheet

On Thu, Jan 20, 2011 at 3:37 PM, Brett Cannon wrote: > On Thu, Jan 20, 2011 at 12:09, M.-A. Lemburg wrote: .. >>>    python/branches/py3k/Misc/cheatsheet >> >> Wouldn't it be better to update this useful file (as part of your >> PSF grant) ? Most of it still applies to Py3. > > That file was not

Re: [Python-Dev] [Python-checkins] devguide: Move Misc/README.Emacs to here.

Hi, On Thu, Jan 20, 2011 at 20:33, brett.cannon wrote: > +.. > +   Local Variables: > +   mode: indented-text > +   indent-tabs-mode: nil > +   sentence-end-double-space: t > +   fill-column: 78 > +   coding: utf-8 > +   End: maybe this can be removed now Cheers, -- Sandro Tosi (aka morph, mor

Re: [Python-Dev] Import and unicode: part two

On 1/20/2011 12:27 PM, Glyph Lefkowitz wrote: To support the latter, could we just make sure that zipimport has a consistent, non-locale-or-operating-system-dependent interpretation of encoding? That way a distributed egg would be importable from a zipfile regardless of how screwed up the distri

Re: [Python-Dev] Import and unicode: part two

On Thu, 20 Jan 2011 15:27:08 -0500 Glyph Lefkowitz wrote: > > To support the latter, could we just make sure that zipimport has a > consistent, > non-locale-or-operating-system-dependent interpretation of encoding? It already has, but it's dependent on a flag in the zip file itself (actually, o

Re: [Python-Dev] Import and unicode: part two

Toshio Kuratomi: > My examples that you're replying to involve two "properly > configured" OS's.  The Linux workstations are configured with a UTF-8 > locale.  The Windows OS's use wide character unicode.  The problem occurs in > that the code that one of the parties develops (either the students

Re: [Python-Dev] [Python-checkins] r88127 - in python/branches/py3k/Misc: README.AIX README.OpenBSD cheatsheet

On Thu, Jan 20, 2011 at 12:09, M.-A. Lemburg wrote: > brett.cannon wrote: >> Author: brett.cannon >> Date: Thu Jan 20 20:34:35 2011 >> New Revision: 88127 >> >> Log: >> Remove some outdated files from Misc. >> >> Removed: >>    python/branches/py3k/Misc/README.AIX > > Are you sure that the AIX REA

Re: [Python-Dev] Import and unicode: part two

On Jan 20, 2011, at 11:46 AM, Guido van Rossum wrote: > On Thu, Jan 20, 2011 at 5:16 AM, Nick Coghlan wrote: >> On Thu, Jan 20, 2011 at 10:08 PM, Simon Cross >> wrote: >>> I'm changing my vote on this to a +1 for two reasons: >>> >>> * Initially I thought this wasn't supported by Python at all

Re: [Python-Dev] [Python-checkins] r88127 - in python/branches/py3k/Misc: README.AIX README.OpenBSD cheatsheet

On Thu, 20 Jan 2011 21:09:47 +0100 "M.-A. Lemburg" wrote: > brett.cannon wrote: > > Author: brett.cannon > > Date: Thu Jan 20 20:34:35 2011 > > New Revision: 88127 > > > > Log: > > Remove some outdated files from Misc. > > > > Removed: > >python/branches/py3k/Misc/README.AIX > > Are you sur

Re: [Python-Dev] Moving stuff out of Misc and over to the devguide

It's not in the svn tree; it's an Hg repo: ssh://h...@hg.python.org/devguide . The link is also listed in the Resources section of the devguide. On Thu, Jan 20, 2011 at 11:59, wrote: > > Brett, > > I'm sure I just missed it, but where is the devguide in the Subversion tree? > > Thx, > > Skip > _

Re: [Python-Dev] [Python-checkins] r88127 - in python/branches/py3k/Misc: README.AIX README.OpenBSD cheatsheet

brett.cannon wrote: > Author: brett.cannon > Date: Thu Jan 20 20:34:35 2011 > New Revision: 88127 > > Log: > Remove some outdated files from Misc. > > Removed: >python/branches/py3k/Misc/README.AIX Are you sure that the AIX README is outdated ? It explains some of the details of why there ar

Re: [Python-Dev] Moving stuff out of Misc and over to the devguide

Brett, I'm sure I just missed it, but where is the devguide in the Subversion tree? Thx, Skip ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/pyt

Re: [Python-Dev] Moving stuff out of Misc and over to the devguide

Short of moving README.coverity (I'm waiting to here back from the company), I'm done with my tweaks to the directory. On Wed, Jan 19, 2011 at 15:31, Brett Cannon wrote: > OK, here is my plan that I will implement: > > MOVE > -- > developers.txt > maintainers.rst > README.gdb > README.cov

Re: [Python-Dev] Import and unicode: part two

On Thu, Jan 20, 2011 at 01:43:03PM -0500, Alexander Belopolsky wrote: > On Thu, Jan 20, 2011 at 12:44 PM, Toshio Kuratomi wrote: > > .. My examples that you're replying to involve two "properly > > configured" OS's.  The Linux workstations are configured with a UTF-8 > > locale.  The Windows OS's

Re: [Python-Dev] [Python-checkins] devguide: Move Misc/maintainers.rst here and rename to experts.rst.

It's just a bit wordy. I simplified it. On Thu, Jan 20, 2011 at 01:22, Sandro Tosi wrote: > Hi, > > On Thu, Jan 20, 2011 at 04:56, brett.cannon > wrote: >> +Unless a name is followed by a '*', you should never assign an issue to >> +that person, only make them nosy.  Names followed by a '*' may

Re: [Python-Dev] [Python-checkins] devguide: Short doc about where to get tech help related to developing Python.

On Wed, Jan 19, 2011 at 15:21, Sandro Tosi wrote: > Hi, > > On Wed, Jan 19, 2011 at 23:19, brett.cannon > wrote: >> +Where to Get Help >> += >> +If you are working on Python it is very possible you will come across an >> issue >> +where you need some assistance in solving (this

Re: [Python-Dev] Import and unicode: part two

On Thu, Jan 20, 2011 at 12:44 PM, Toshio Kuratomi wrote: > .. My examples that you're replying to involve two "properly > configured" OS's.  The Linux workstations are configured with a UTF-8 > locale.  The Windows OS's use wide character unicode.  The problem occurs in > that the code that one of

Re: [Python-Dev] Import and unicode: part two

On Thu, Jan 20, 2011 at 11:45 AM, Andy Teijelo wrote: .. > but if the code said: > > import café > > then Python would look, in any platform, for a file named: > > café.py  or  café.py  or something nicer. > > Something along the lines of xmlcharrefreplace. > Just an idea. Curiously, something li

Re: [Python-Dev] Import and unicode: part two

On Thu, Jan 20, 2011 at 12:51:29PM +0100, Victor Stinner wrote: > Le mercredi 19 janvier 2011 à 20:39 -0800, Toshio Kuratomi a écrit : > > Teaching students to write non-portable code (relying on filesystem encoding > > where your solution is, don't upload to pypi anything that has non-ascii > > fi

Re: [Python-Dev] Import and unicode: part two

(Hi, I'm writing from an address different to the one I'm subscribed with to the list because I don't have reverse dns in my mail server and mail.python.org rejects my messages. I hope that's not much trouble) Maybe Python should always use an ASCII encodable filename for modules: a translatio

Re: [Python-Dev] Import and unicode: part two

On Thu, Jan 20, 2011 at 5:16 AM, Nick Coghlan wrote: > On Thu, Jan 20, 2011 at 10:08 PM, Simon Cross > wrote: >> I'm changing my vote on this to a +1 for two reasons: >> >> * Initially I thought this wasn't supported by Python at all but I see >> that currently it is supported but that support is

Re: [Python-Dev] r88122 - python/branches/py3k/Doc/whatsnew/3.2.rst

On Thu, 20 Jan 2011 15:59:39 +0200 Nadeem Vawda wrote: > On Thu, Jan 20, 2011 at 3:11 PM, Antoine Pitrou wrote: > > On Thu, 20 Jan 2011 10:47:04 +0100 (CET) > > raymond.hettinger wrote: > >> > >> +Code Repository > >> +=== > >> + > >> +In addition to the existing Subversion code repo

Re: [Python-Dev] r88122 - python/branches/py3k/Doc/whatsnew/3.2.rst

On Thu, Jan 20, 2011 at 3:11 PM, Antoine Pitrou wrote: > On Thu, 20 Jan 2011 10:47:04 +0100 (CET) > raymond.hettinger wrote: >> >> +Code Repository >> +=== >> + >> +In addition to the existing Subversion code repository at >> http://svn.python.org >> +there is now a `Mercurial

Re: [Python-Dev] [Python-checkins] r88121 - python/branches/py3k/Doc/whatsnew/3.2.rst

On Thu, Jan 20, 2011 at 10:41 PM, Victor Stinner wrote: > Le jeudi 20 janvier 2011 à 10:04 +0100, raymond.hettinger a écrit : >> +Some operating systems allow direct access to the unencoded bytes in the >> +environment.  If so, the :attr:`os.supports_bytes_environ` constant will be >> +true. >> +

Re: [Python-Dev] Import and unicode: part two

On Thu, Jan 20, 2011 at 10:08 PM, Simon Cross wrote: > I'm changing my vote on this to a +1 for two reasons: > > * Initially I thought this wasn't supported by Python at all but I see > that currently it is supported but that support is broken (or at least > limited to UTF-8 filesystem encodings).

Re: [Python-Dev] r88122 - python/branches/py3k/Doc/whatsnew/3.2.rst

On Thu, 20 Jan 2011 10:47:04 +0100 (CET) raymond.hettinger wrote: > > +Code Repository > +=== > + > +In addition to the existing Subversion code repository at > http://svn.python.org > +there is now a `Mercurial `_ repository at > +http://hg.python.org

Re: [Python-Dev] [Python-checkins] r88121 - python/branches/py3k/Doc/whatsnew/3.2.rst

Le jeudi 20 janvier 2011 à 10:04 +0100, raymond.hettinger a écrit : > +Some operating systems allow direct access to the unencoded bytes in the > +environment. If so, the :attr:`os.supports_bytes_environ` constant will be > +true. > + > +For direct access to unencoded environment variables (if ava

Re: [Python-Dev] Import and unicode: part two

On Wed, Jan 19, 2011 at 5:01 PM, Simon Cross wrote: > On Wed, Jan 19, 2011 at 2:34 PM, Victor Stinner > wrote: >>  (a) Python 3 doesn't support non-ASCII module names > > -0: I'm vaguely against this being supported because I'd rather not > have to deal with what happens when the guess regarding

Re: [Python-Dev] [Python-checkins] r88119 - in python/branches/py3k/Doc: library/inspect.rst whatsnew/3.2.rst

Le jeudi 20 janvier 2011 à 05:03 +0100, raymond.hettinger a écrit : > * Python's import mechanism can now load modules installed in directories > with > - non-ASCII characters in the path name. > + non-ASCII characters in the path name: > + > + >>> import møøse.bites > >(Required extensi

Re: [Python-Dev] Import and unicode: part two

Le mercredi 19 janvier 2011 à 20:39 -0800, Toshio Kuratomi a écrit : > Teaching students to write non-portable code (relying on filesystem encoding > where your solution is, don't upload to pypi anything that has non-ascii > filenames) seems like the exact opposite of how you'd want to shape a youn

Re: [Python-Dev] Import and unicode: part two

On Jan 19, 2011, at 11:39 PM, Toshio Kuratomi wrote: > Tangent: This is not true about Linux. UTF-8 is a matter of the > interpretation of the filesystem bytes that the user specifies by setting > their system locale. Setting system locale to ASCII for use in system-wide > scripts, is quite commo

Re: [Python-Dev] [Python-checkins] devguide: Move Misc/maintainers.rst here and rename to experts.rst.

Hi, On Thu, Jan 20, 2011 at 04:56, brett.cannon wrote: > +Unless a name is followed by a '*', you should never assign an issue to > +that person, only make them nosy.  Names followed by a '*' may be assigned > +issues involving the module or topic for which the name has a '*'. isn't last sentenc