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

2011-01-24 Thread Fred Drake
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] Keeping __init__.py empty for Python packages used for module grouping.

2011-01-24 Thread Brett Cannon
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] Keeping __init__.py empty for Python packages used for module grouping.

2011-01-24 Thread Martin v. Löwis
> 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.

2011-01-24 Thread Terry Reedy
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] Keeping __init__.py empty for Python packages used for module grouping.

2011-01-24 Thread Tres Seaver
-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] Keeping __init__.py empty for Python packages used for module grouping.

2011-01-24 Thread Fred Drake
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] Keeping __init__.py empty for Python packages used for module grouping.

2011-01-24 Thread Georg Brandl
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.

2011-01-24 Thread 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 related modules, html.parser and html.entities. ISTM, that i