On Fri, Apr 28, 2006 at 01:13:21AM +0200, thomas.wouters wrote:
- Warn-raise ImportWarning when importing would have picked up a directory
as package, if only it'd had an __init__.py. This swaps two tests (for
case-ness and __init__-ness), but case-test is not really more expensive,
A.M. Kuchling wrote:
On Fri, Apr 28, 2006 at 01:13:21AM +0200, thomas.wouters wrote:
- Warn-raise ImportWarning when importing would have picked up a directory
as package, if only it'd had an __init__.py. This swaps two tests (for
case-ness and __init__-ness), but case-test is not
A.M. Kuchling wrote:
On Fri, Apr 28, 2006 at 01:13:21AM +0200, thomas.wouters wrote:
- Warn-raise ImportWarning when importing would have picked up a directory
as package, if only it'd had an __init__.py. This swaps two tests (for
case-ness and __init__-ness), but case-test is not
On 4/29/06, Nick Coghlan [EMAIL PROTECTED] wrote:
So the relatively non-controversial bit (improving the error reporting) wasadded immediately, and the controversial bit postponed to see if the bettererror reporting had any effect on the demand for it.
This is exactly how I intended it, and I
Actually after all the -1 responses I wasn't going to reconsider this
for 2.x; maybe for py3k. Most of the -1 votes were unconditional; only
a few respondents thought that I was proposing it for 2.5.
--Guido
On 4/29/06, Thomas Wouters [EMAIL PROTECTED] wrote:
On 4/29/06, Nick Coghlan [EMAIL
Guido van Rossum [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Actually after all the -1 responses I wasn't going to reconsider this
for 2.x; maybe for py3k.
I think there may be proposals to review and possibly revise the packing
and import mechanisms for 3.0. So I think your
I may be misunderstanding what you wrote. I thought that packing and
join were *only* being discussed in a py3k context? If they are being
discussed in a 2.x context, then yes, these discussions ought to be
moved to py3k.
--Guido
On 4/29/06, Terry Reedy [EMAIL PROTECTED] wrote:
Guido van
