Re: [Python-Dev] Location of tests for packages

Am 25.01.2011 02:19, schrieb Raymond Hettinger: > > On Jan 24, 2011, at 3:40 PM, Michael Foord wrote: >> It isn't just unittest, it seems that all *test packages* are in their >> respective package and not Lib/test except for the json module where Raymond >> already moved the tests: >> >>di

Re: [Python-Dev] Location of tests for packages

Am 25.01.2011 00:14, schrieb "Martin v. Löwis": >>> This isn't a critical issue (nothing is broken) but we're a week >>> from another release candidate, so the new Py3.2 package >>> organization (unittest was flat in Py3.1 and its test were under >>> Lib/test) is about to become a de-facto decision

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

On Mon, Jan 24, 2011 at 4:59 PM, Tres Seaver wrote: > It might matter if we want to enable third-party package installation > into a namespace also used by the stdlib:  ISTR that the 'xml' package > had such installs at one point. Almost, but not quite. The xml package at one point allowed itsel

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

On Thu, Jan 20, 2011 at 03:27:08PM -0500, Glyph Lefkowitz wrote: > > On Jan 20, 2011, at 11:46 AM, Guido van Rossum wrote: > Same here. *Most* code will never be shared, or will only be shared > between users in the same community. When it goes wrong it's also a > learning opportunity.

Re: [Python-Dev] Location of tests for packages

On Jan 24, 2011, at 3:40 PM, Michael Foord wrote: > It isn't just unittest, it seems that all *test packages* are in their > respective package and not Lib/test except for the json module where Raymond > already moved the tests: > >distutils/tests >email/test >ctypes/test >impor

Re: [Python-Dev] PEP 393: Flexible String Representation

On Mon, 2011-01-24 at 21:17 +0100, "Martin v. Löwis" wrote: ... snip ... > I'd like to propose PEP 393, which takes a different approach, > addressing both problems simultaneously: by getting a flexible > representation (one that can be either 1, 2, or 4 bytes), we can > support the full range of

Re: [Python-Dev] Location of tests for packages

On 24/01/2011 23:14, "Martin v. Löwis" wrote: This isn't a critical issue (nothing is broken) but we're a week from another release candidate, so the new Py3.2 package organization (unittest was flat in Py3.1 and its test were under Lib/test) is about to become a de-facto decision that will be ha

Re: [Python-Dev] Location of tests for packages

On 24/01/2011 19:46, Raymond Hettinger wrote: Right now, the tests for the unittest package are under the package directory instead of Lib/test where we have most of the other tests. There are some other packages that do the same thing, each for their own reason. I think we should develop a st

Re: [Python-Dev] Location of tests for packages

Le mardi 25 janvier 2011 à 00:14 +0100, "Martin v. Löwis" a écrit : > >> This isn't a critical issue (nothing is broken) but we're a week > >> from another release candidate, so the new Py3.2 package > >> organization (unittest was flat in Py3.1 and its test were under > >> Lib/test) is about to be

Re: [Python-Dev] PEP 393: Flexible String Representation

Le mardi 25 janvier 2011 à 00:07 +0100, "Martin v. Löwis" a écrit : > >> I'd like to propose PEP 393, which takes a different approach, > >> addressing both problems simultaneously: by getting a flexible > >> representation (one that can be either 1, 2, or 4 bytes), we can > >> support the full ran

Re: [Python-Dev] Location of tests for packages

>> This isn't a critical issue (nothing is broken) but we're a week >> from another release candidate, so the new Py3.2 package >> organization (unittest was flat in Py3.1 and its test were under >> Lib/test) is about to become a de-facto decision that will be hard >> to undo. > > Well can we stop

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

On Mon, Jan 24, 2011 at 11:18, Georg Brandl wrote: > Am 24.01.2011 20:04, schrieb Raymond Hettinger: >> Looking at http://docs.python.org/dev/library/html.html#module-html it would >> appear that we've created a new module with a single trivial function. >> >> In reality, there was already a pytho

Re: [Python-Dev] PEP 393: Flexible String Representation

>> I'd like to propose PEP 393, which takes a different approach, >> addressing both problems simultaneously: by getting a flexible >> representation (one that can be either 1, 2, or 4 bytes), we can >> support the full range of Unicode on all systems, but still use >> only one byte per character f

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

> If that pattern is a goal, having all versions of the namespace's > __init__.py empty of anything but the __path__-munging majyk / > boilerplate is required to make such installs work regardless of the > order of PYTHONPATH. With PEP 382, having extensible packages won't contradict to having a n

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

On 1/24/2011 2:18 PM, Georg Brandl wrote: Am 24.01.2011 20:04, schrieb Raymond Hettinger: Looking at http://docs.python.org/dev/library/html.html#module-html it would appear that we've created a new module with a single trivial function. In reality, there was already a python package, html, tha

Re: [Python-Dev] Location of tests for packages

2011/1/24 Éric Araujo : >> Right now, the tests for the unittest package are under the >> package directory instead of Lib/test where we have most of the >> other tests. >> >> There are some other packages that do the same thing, each for >> their own reason. > > The corresponding bug report is #10

Re: [Python-Dev] PEP 393: Flexible String Representation

On Mon, 24 Jan 2011 21:17:34 +0100 "Martin v. Löwis" wrote: > I have been thinking about Unicode representation for some time now. > This was triggered, on the one hand, by discussions with Glyph Lefkowitz > (who complained that his server app consumes too much memory), and Carl > Friedrich Bolz (

Re: [Python-Dev] Location of tests for packages

On Mon, 24 Jan 2011 11:46:45 -0800 Raymond Hettinger wrote: > > This isn't a critical issue (nothing is broken) but we're a week from another > release candidate, so the new Py3.2 package organization (unittest was flat > in Py3.1 and its test were under Lib/test) is about to become a de-facto

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/24/2011 03:14 PM, Fred Drake wrote: > On Mon, Jan 24, 2011 at 2:04 PM, Raymond Hettinger > wrote: >> ISTM, that if we're going to use python packages as "namespace containers" >> for >> categorizing modules, then the top level __init__ namespac

Re: [Python-Dev] Location of tests for packages

On Jan 24, 2011, at 11:46 AM, Raymond Hettinger wrote: >P.S. I've discussed this with Michael and his preference is against going >back to the Py3.1 style where the tests were under Lib/test. He thinks the >current tree makes it easier to sync with Py2.7 and the unittest2 third-party >module. A

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

Am 24.01.2011 16:39, schrieb Victor Stinner: > Le lundi 24 janvier 2011 11:35:22, Stephen J. Turnbull a écrit : >> ... VFAT-formatted file systems and Shift JIS file names ... > > I missed something: VFAT stores filenames as unicode (whereas FAT only > supports byte filenames). Well, VFAT stores

Re: [Python-Dev] Location of tests for packages

On Mon, Jan 24, 2011 at 2:46 PM, Raymond Hettinger wrote: > P.S.  I've discussed this with Michael and his preference is against > going back to the Py3.1 style where the tests were under Lib/test.  He > thinks the current tree makes it easier to sync with Py2.7 and the > unittest2 third-party mod

[Python-Dev] PEP 393: Flexible String Representation

I have been thinking about Unicode representation for some time now. This was triggered, on the one hand, by discussions with Glyph Lefkowitz (who complained that his server app consumes too much memory), and Carl Friedrich Bolz (who profiled Python applications to determine that Unicode strings ar

Re: [Python-Dev] Location of tests for packages

> Right now, the tests for the unittest package are under the > package directory instead of Lib/test where we have most of the > other tests. > > There are some other packages that do the same thing, each for > their own reason. The corresponding bug report is #10572 (opened by Michael Foord).

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

On Mon, Jan 24, 2011 at 2:04 PM, Raymond Hettinger wrote: > ISTM, that if we're going to use python packages as "namespace containers" for > categorizing modules, then the top level __init__ namespace should be left > empty. This is only an issue if the separate components are distributed separa

Re: [Python-Dev] What's new 2.x in 3.x docs.

Am 23.01.2011 02:48, schrieb Nick Coghlan: > On Sun, Jan 23, 2011 at 7:23 AM, Raymond Hettinger > wrote: >> On Jan 22, 2011, at 11:04 AM, Terry Reedy wrote: >> >>> The 3.x docs mostly started fresh with 3.0. The major exception is the >>> What's new section, which goes back to 2.0. The 2.x stuff

[Python-Dev] Location of tests for packages

Right now, the tests for the unittest package are under the package directory instead of Lib/test where we have most of the other tests. There are some other packages that do the same thing, each for their own reason. I think we should develop a strong preference for tests going under Lib/test

Re: [Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

Am 24.01.2011 20:04, schrieb Raymond Hettinger: > Looking at http://docs.python.org/dev/library/html.html#module-html it would > appear that we've created a new module with a single trivial function. > > In reality, there was already a python package, html, that served to group > two loosely relat

[Python-Dev] Keeping __init__.py empty for Python packages used for module grouping.

Looking at http://docs.python.org/dev/library/html.html#module-html it would appear that we've created a new module with a single trivial function. In reality, there was already a python package, html, that served to group two loosely related modules, html.parser and html.entities. ISTM, that i

Re: [Python-Dev] Beta version of the new devguide

On Mon, Jan 24, 2011 at 07:46, Antoine Pitrou wrote: > On Sat, 22 Jan 2011 17:08:00 -0800 > Brett Cannon wrote: >> >> Two, what should the final URL be? Georg picked the current one and I >> am happy with it. > > Ditto for me. > >> Three, where should it be linked from? docs.python.org homepage?

Re: [Python-Dev] Beta version of the new devguide

On Mon, Jan 24, 2011 at 07:33, Nick Coghlan wrote: > On Mon, Jan 24, 2011 at 9:29 PM, Antoine Pitrou wrote: >> On Mon, 24 Jan 2011 20:33:07 +1000 >> Nick Coghlan wrote: >>> On Mon, Jan 24, 2011 at 6:22 AM, Brett Cannon wrote: >>> >> In "Getting Set Up" it describes how to build a pydebug build.

Re: [Python-Dev] (no subject)

Bug reports should be filed at bugs.python.org On Mon, Jan 24, 2011 at 08:39, Stefan Spoettl wrote: > Using: > Python 2.7.0+ (r27:82500, Sep 15 2010, 18:14:55) > [GCC 4.4.5] on linux2 > (Ubuntu 10.10) > Method to reproduce error: > 1. Defining a module which is later imported by another: > --

Re: [Python-Dev] (no subject)

On Mon, Jan 24, 2011 at 04:39:54PM +, Stefan Spoettl wrote: > So it may be that the Python interpreter isn't working correctly onlyon > Ubuntu 10.10 Than you should report the problem to the Ubuntu developers, right? And it would be nice if you investigate deeper and send a proper mail - w

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

On Mon, Jan 24, 2011 at 04:39:39PM +0100, Victor Stinner wrote: > I missed something: VFAT stores filenames as unicode (whereas FAT only > supports byte filenames). Well, VFAT stores filenames twice: as a 8+3 byte > strings and as a 255 unicode (UTF-16-LE) string (UTF-16-LE). > > On which OS do

Re: [Python-Dev] tahoe-lafs

I want to make it clear that I am in no way associated with the tahoe-lafs project. I do not want my email to make that project look bad. That was not my intention. Billy Earney ear...@umsystem.edu Programmer/Analyst-Expert [cid:image001.gif@01C0.03DD8B00] MySQ

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

Le lundi 24 janvier 2011 16:39:39, Victor Stinner a écrit : > Le lundi 24 janvier 2011 11:35:22, Stephen J. Turnbull a écrit : > > ... VFAT-formatted file systems and Shift JIS file names ... > > I missed something: VFAT stores filenames as unicode (whereas FAT only > supports byte filenames). Wel

[Python-Dev] (no subject)

Using:Python 2.7.0+ (r27:82500, Sep 15 2010, 18:14:55) [GCC 4.4.5] on linux2(Ubuntu 10.10) Method to reproduce error: 1. Defining a module which is later imported by another: - class SomeThing: def __init__(self):self

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

Le lundi 24 janvier 2011 11:35:22, Stephen J. Turnbull a écrit : > ... VFAT-formatted file systems and Shift JIS file names ... I missed something: VFAT stores filenames as unicode (whereas FAT only supports byte filenames). Well, VFAT stores filenames twice: as a 8+3 byte strings and as a 255 u

Re: [Python-Dev] Beta version of the new devguide

On Sat, 22 Jan 2011 17:08:00 -0800 Brett Cannon wrote: > > Two, what should the final URL be? Georg picked the current one and I > am happy with it. Ditto for me. > Three, where should it be linked from? docs.python.org homepage? > Four, what to do with www.python.org/dev/? Redirect for all the

Re: [Python-Dev] tahoe-lafs

On Mon, Jan 24, 2011 at 11:56 PM, Earney, Billy C. wrote: > Greetings! > > > > I know that this list is for python development questions/comments, > People that post questions innocently unaware of the nature of this list have an excuse. You don't. This is not a good way to encourage people to

Re: [Python-Dev] Beta version of the new devguide

On Mon, Jan 24, 2011 at 9:29 PM, Antoine Pitrou wrote: > On Mon, 24 Jan 2011 20:33:07 +1000 > Nick Coghlan wrote: >> On Mon, Jan 24, 2011 at 6:22 AM, Brett Cannon wrote: >> >> In "Getting Set Up" it describes how to build a pydebug build. Is that >> >> really necessary for those who plan only to

Re: [Python-Dev] tahoe-lafs

On Mon, 24 Jan 2011 07:56:56 -0600 "Earney, Billy C." wrote: > Greetings! > > I know that this list is for python development questions/comments, but I > wanted to bring up the tahoe-lafs project [...] You should really post such messages to comp.lang.python. _

[Python-Dev] tahoe-lafs

Greetings! I know that this list is for python development questions/comments, but I wanted to bring up the tahoe-lafs project if people are interested in a project developed in python that allows for secure distributed storage. For more information see http://tahoe-lafs.org For those of you

Re: [Python-Dev] Beta version of the new devguide

On Mon, 24 Jan 2011 20:33:07 +1000 Nick Coghlan wrote: > On Mon, Jan 24, 2011 at 6:22 AM, Brett Cannon wrote: > >> In "Getting Set Up" it describes how to build a pydebug build. Is that > >> really necessary for those who plan only to contribute by working on > >> pure Python code? > >> > > > > Y

Re: [Python-Dev] Beta version of the new devguide

Hi Brett, On Sat, 22 Jan 2011 17:08:00 -0800 Brett Cannon wrote: > http://docs.python.org/devguide/ Personally, I found the first paragraph of "Contributing" a bit off-putting. How about replacing: People who wish to contribute to Python must read the following documents in the order p

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

On Mon, Jan 24, 2011 at 8:35 PM, Stephen J. Turnbull wrote: > First of all, these aren't just phones; these are all kinds of gadgets > (the example I gave was a camera).  They're not as smart as an Android > or iPhone-like device, and I don't know what OS they use. We're getting a little far afie

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

"Martin v. Löwis" writes: > It's one thing how the file systems are formatted, but another thing > how they are presented to APIs. For example, the phones using Windows CE > would have to convert the file names to Unicode in the OS kernel. > > So: for these phones - do you know how they pres

Re: [Python-Dev] Beta version of the new devguide

On Mon, Jan 24, 2011 at 6:22 AM, Brett Cannon wrote: >> In "Getting Set Up" it describes how to build a pydebug build. Is that >> really necessary for those who plan only to contribute by working on >> pure Python code? >> > > Yes, there is actually a laundry list of reasons even people only > wor

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

> > Really? I would have thought that cell phones have long been the > > platforms most supportive of Unicode. > > I would think so too, except in Japan. > > However, my previous phones exposed file systems with names encoded in > Shift JIS to USB and IR browsers, though. (My current one uses

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

Guido van Rossum writes: > Really? I would have thought that cell phones have long been the > platforms most supportive of Unicode. I would think so too, except in Japan. However, my previous phones exposed file systems with names encoded in Shift JIS to USB and IR browsers, though. (My curre