[issue2306] Update What's new in 3.0

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

Some small mistakes :

* « an object always compares equal to itself (i.e., ``x is y`` implies
``x == y``; this is true even for *NaN*) ». Actually NaN is not equal to
itself:

True
>>> f == f
False

* « The traceback printed when an unhandled exception occurs walks the
chain of :attr:`__cause__` and :attr:`__context__` attributes and prints
a separate traceback for each component of the chain, with the primary
exception at the top. » If by "primary exception" you mean the latest
one, then it's printed at the bottom, not the top.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4497] Compiler warnings in longobject.c

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

This is on Windows, right?  I don't know of any other platforms where 
__int64 is defined.

At a first glance, it looks as though the code's correct, so we probably 
just need to add some casts to silence the compiler.  I'll add them to the 
patch in issue 4393 and check it in sometime soon after 3.0 is released.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4497] Compiler warnings in longobject.c

[Mark Dickinson]

Changes by Mark Dickinson <[EMAIL PROTECTED]>:


--
versions: +Python 2.6, Python 2.7, Python 3.1

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4500] Compiler warnings when compiling Python 3.0 with a C89 compiler

[Christian Heimes]

Christian Heimes <[EMAIL PROTECTED]> added the comment:

I'm Ubuntu 8.10 AMD64.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4273] cycle created by profile.run

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

But the garbage collector was invented for this very purpose: to break
cycles! Take the following example which create a cycle for every
instance of the class (the profile module has similar code):

class C:
def __init__(self):
self.action = self.action_GO
# cycle: the object's dict now contains a bound method 
# which references the object
def action_GO(self):
print("GO")

This kind of construct is useful, and probably the best one in some
cases. Would you ban it from your code? from the python standard library?

Reference cycles are not bad at all, as long as they only hold memory:
they will be reclaimed when the systems needs more memory. 

I agree that they can be a problem for other valuable resource: opened
files, sockets, database cursors... even one thousand of uncollected
sockets are not enough to trigger a collection.
For this usage, I suggest that you iterate over gc.garbage, only warn
for such objects and remove all others (and after, clear gc.garbage and
run gc.collect() without the debug flag)

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4393] Portability fixes in longobject.c

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

See also issue 4497 for some compiler warnings that need to be silenced.

--
assignee:  -> marketdickinson

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

[Marc-Andre Lemburg]

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment:

On 2008-12-03 01:44, Christian Heimes wrote:
> Christian Heimes <[EMAIL PROTECTED]> added the comment:
> 
> Barry, the issue in _ctypes/callproc.c could be a problem for us
> although Python 2.6 and 3.0 are compiling fine with -std=c89. Should the
> comment be fixed before the release?

I had a second look at the code. That comment is in #ifdefs:

#ifdef MS_WIN32
...
#endif

so it won't affect compiling ctypes on Unix platforms.

Still, I find the situation with C99 comments scattered around the
source code less than ideal. Either we officially abandon C90 and move
on to C99 or we stick to C90 for all source code (including code that
only gets compiled on Macs or MSVC).

It's just too easy for a C99 comment to slip into code that's
targeted for non-gcc/non-MSVC compilers as well and these then
break the portability of Python to those compilers/platforms.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4503] exception traceback sometimes slow

[Hirokazu Yamamoto]

New submission from Hirokazu Yamamoto <[EMAIL PROTECTED]>:

Please try this code.

import zipfile
zipfile.PyZipFile("foobar")

I'm not sure this is problematic or not.

--
messages: 76823
nosy: ocean-city
severity: normal
status: open
title: exception traceback sometimes slow
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4503] exception traceback sometimes slow

[Antoine Pitrou]

Antoine Pitrou <[EMAIL PROTECTED]> added the comment:

What do you mean by "slow"? I can't reproduce under Linux.

--
nosy: +pitrou

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1615] descriptor protocol bug

[ganges master]

ganges master <[EMAIL PROTECTED]> added the comment:

here's a short example of the bug

>>> class Foo(object):
...   def __getattr__(self, name): 
... return 42
...   @property
...   def bacon(self): 
... return int.lalala
...   @property
...   def eggs(self): 
... return 17
... 
>>> f = Foo()
>>> f.bacon   # raises an AttributeError, and silently ignores it
42
>>> f.eggs
17
>>> 

are there any news in this front?

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4503] exception traceback sometimes slow

[Hirokazu Yamamoto]

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment:

Traceback (most recent call last):
  File "a.py", line 4, in 
zipfile.PyZipFile("foobar")
  File "e:\python-dev\py3k\lib\zipfile.py", line 683, in __init__
self.fp = io.open(file, modeDict[mode])
  File "e:\python-dev\py3k\lib\io.py", line 222, in open
closefd)
  File "e:\python-dev\py3k\lib\io.py", line 615, in __init__
_fileio._FileIO.__init__(self, name, mode, closefd)
IOError: [Errno 2] No such file or directory: 'foobar'
[33393 refs]

For example, some delay after

   File "e:\python-dev\py3k\lib\zipfile.py", line 683, in __init__

this line. I don't know why, but maybe because current io module is not
written in C.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4503] exception traceback sometimes slow

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

Is "e:" a network drive? This could explain the delay.

But it's true that the code that displays the exception has to call
readline() 683 times, and this code is written in python. There is a
project to rewrite io.py in C...

Also, you are using a debug build. Is the slowdown still noticeable with
a release build?

--
nosy: +amaury.forgeotdarc

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4504] Doc/includes out of date

[Kandalintsev Alexandre]

New submission from Kandalintsev Alexandre <[EMAIL PROTECTED]>:

Hello!

Doc/includes/noddy.c and all other uses Py_InitModule3 which is removed 
from py3k.

noddy2.c doesn't compile("noddy2.c:16: error: ‘Noddy’ has no member 
named ‘ob_type’").

--
assignee: georg.brandl
components: Documentation
messages: 76828
nosy: exe, georg.brandl
severity: normal
status: open
title: Doc/includes out of date
type: compile error
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4505] ob_size not removed from docs

[Kandalintsev Alexandre]

New submission from Kandalintsev Alexandre <[EMAIL PROTECTED]>:

Hello!

In http://docs.python.org/dev/3.0/extending/newtypes.html we see ob_size 
in object definition.

But if we are look on PyTypeObject in ./Include/object.h we will find 
that there no ob_size defined.


So we must remove this string from noddy_NoddyType definition or segfault 
will occur:
0, /*ob_size*/

--
assignee: georg.brandl
components: Documentation
messages: 76829
nosy: exe, georg.brandl
severity: normal
status: open
title: ob_size not removed from docs
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3890] ssl.SSLSocket.recv() implementation may not work with non-blocking sockets

[Giampaolo Rodola']

Giampaolo Rodola' <[EMAIL PROTECTED]> added the comment:

Wouldn't it be better to fix this before 3.0 gets released?

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1541] Bad OOB data management when using asyncore with select.poll()

[Giampaolo Rodola']

Giampaolo Rodola' <[EMAIL PROTECTED]> added the comment:

This is a duplicate of #4501 which provides a better patch.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3890] ssl.SSLSocket.recv() implementation may not work with non-blocking sockets

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment:

I fear that is is too late for 3.0: the branch is already "frozen",
except maybe for special cases.

In any case a patch is needed. 
I am not a ssl expert, I just implemented the "let SSL_ERROR_WANT_READ
propagate".
Please review.

--
keywords: +needs review, patch
nosy: +amaury.forgeotdarc
Added file: http://bugs.python.org/file12210/ssl_noblock.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4025] C99 comments in Python 2.6 break build on AIX 6.1

[Andrew Paprocki]

Andrew Paprocki <[EMAIL PROTECTED]> added the comment:

The list of files/lines I posted yesterday was all that I had to change
to get it to build here (where a C++ style comment is a syntax error),
so it doesn't seem like a massive change.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2306] Update What's new in 3.0

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

On Wed, Dec 3, 2008 at 1:36 AM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
> Antoine Pitrou <[EMAIL PROTECTED]> added the comment:
>
> Some small mistakes :
>
> * « an object always compares equal to itself (i.e., ``x is y`` implies
> ``x == y``; this is true even for *NaN*) ». Actually NaN is not equal to
> itself:
>
> True
 f == f
> False

Raymond pointed this out too and I fixed it before Barry got to the tagging.

> * « The traceback printed when an unhandled exception occurs walks the
> chain of :attr:`__cause__` and :attr:`__context__` attributes and prints
> a separate traceback for each component of the chain, with the primary
> exception at the top. » If by "primary exception" you mean the latest
> one, then it's printed at the bottom, not the top.

No, I mean the first one (as the example tries to clarify).

Thanks for reviewing! I definitely cut it too close this time, due to
various other commitments. :-(

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2306] Update What's new in 3.0

[Guido van Rossum]

Guido van Rossum <[EMAIL PROTECTED]> added the comment:

I think this is good enough for now.

Someone else can help add stuff I missed, but I don't think we need to
keep a bug open to remind us.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4503] exception traceback sometimes slow

[Hirokazu Yamamoto]

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment:

No, e: is not netword drive. It's another partition on hard drive. But
my machine is pretty slow.

>Also, you are using a debug build. Is the slowdown still noticeable with
>a release build?

I tried release build(VC6), and was much faster.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4201] Pdb cannot access source code in zipped packages.

[Nick Coghlan]

Changes by Nick Coghlan <[EMAIL PROTECTED]>:


--
assignee:  -> ncoghlan
nosy: +ncoghlan

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4197] Doctest module does not work with zipped packages

[Nick Coghlan]

Changes by Nick Coghlan <[EMAIL PROTECTED]>:


--
assignee:  -> ncoghlan
nosy: +ncoghlan

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4223] inspect.getsource doesn't work on functions imported from a zipfile

[Nick Coghlan]

Changes by Nick Coghlan <[EMAIL PROTECTED]>:


--
assignee:  -> ncoghlan
nosy: +ncoghlan

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4197] Doctest module does not work with zipped packages

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

runpy needs a non-standard PEP 302 extension to set __file__ correctly
in the modules it runs. The pkgutil stuff it uses to find pure Python
modules in the filesystem supports that extension, but zipimport doesn't
(yet).

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4201] Pdb cannot access source code in zipped packages.

[Nick Coghlan]

Nick Coghlan <[EMAIL PROTECTED]> added the comment:

Just to confirm - this is specific to __main__.py right?

The problem is actually with runpy not being able to set __file__
correctly, rather than being pdb specific.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Skip Montanaro]

New submission from Skip Montanaro <[EMAIL PROTECTED]>:

I downloaded the 3.0 tarfile and did a straightforward

configure
make
make test

on Solaris 10 and got several test failures:

290 tests OK.
4 tests failed:
test_cmath test_math test_posix test_subprocess

Here's the output for just the failing tests:

test test_cmath failed -- Traceback (most recent call last):
  File "/home/tuba/skipm/src/Python-3.0/Lib/test/test_cmath.py", line 336,
  in test_specific_values
self.fail('OverflowError not raised in test %s' % test_str)
AssertionError: OverflowError not raised in test exp0052: exp(complex(710.0,
1.5))

test test_math failed -- errors occurred; run in verbose mode for details

test test_posix failed -- Traceback (most recent call last):
  File "/home/tuba/skipm/src/Python-3.0/Lib/test/test_posix.py", line 252,
  in test_getcwd_long_pathnames
support.rmtree(base_path)
  File "/home/tuba/skipm/src/Python-3.0/Lib/test/support.py", line 98, in
  rmtreeshutil.rmtree(path)
  File "/home/tuba/skipm/src/Python-3.0/Lib/shutil.py", line 225, in rmtree
onerror(os.rmdir, path, sys.exc_info())
  File "/home/tuba/skipm/src/Python-3.0/Lib/shutil.py", line 223, in rmtree
os.rmdir(path)
OSError: [Errno 22] Invalid argument:
'/home/tuba/skipm/src/Python-3.0/@test.getcwd'

Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
Fatal Python error: Py_Initialize: can't initialize sys standard streams
ImportError: No module named encodings.utf_8
.
this bit of output is from a test of stdout in a different process ...
test test_subprocess failed -- Traceback (most recent call last):
  File "/home/tuba/skipm/src/Python-3.0/Lib/test/test_subprocess.py", line
  115, in test_executable
self.assertEqual(p.returncode, 47)
AssertionError: -6 != 47

Here's the test_math output run through regrtest with the -v option:

==
FAIL: testLog (test.test_math.MathTests)
--
Traceback (most recent call last):
  File "/home/tuba/skipm/src/Python-3.0/Lib/test/test_math.py", line 510, in
  testLog
self.assertRaises(ValueError, math.log, NINF)
AssertionError: ValueError not raised by log

==
FAIL: testLog10 (test.test_math.MathTests)
--
Traceback (most recent call last):
  File "/home/tuba/skipm/src/Python-3.0/Lib/test/test_math.py", line 532, in
  testLog10
self.assertRaises(ValueError, math.log10, NINF)
AssertionError: ValueError not raised by log10

--
Ran 39 tests in 0.294s

Skip

--
messages: 76839
nosy: skip.montanaro
severity: normal
status: open
title: 3.0 make test failures on Solaris 10

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

I think you brought up the math and cmath errors before, and I never 
managed to get to the bottom of the problem.  I'll have another go.

I don't think the (c)math test failures should be regarded as terribly 
serious, though;  the tests are quite ridiculously strict.

Could you please tell me what

cmath.exp(complex(710.0, 1.5))

actually returns, if it doesn't raise OverflowError?

(Don't know nuffin about posix and subprocess.)

--
nosy: +marketdickinson

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Skip Montanaro]

Skip Montanaro <[EMAIL PROTECTED]> added the comment:

Mark> I think you brought up the math and cmath errors before, and I
Mark> never managed to get to the bottom of the problem.  I'll have
Mark> another go.

I vaguely remember something about that.  If I can be a "test mule" for you,
let me know.

Mark> Could you please tell me what

Mark> cmath.exp(complex(710.0, 1.5))

Mark> actually returns, if it doesn't raise OverflowError?

(1.5802653829857376e+307+inf*j)

Maybe it needs to overflow along both axes???

S

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4507] 3.0 test failure on Mac OS X 10.5.5

[Skip Montanaro]

New submission from Skip Montanaro <[EMAIL PROTECTED]>:

After seeing test failures on Solaris 10 (issue4506) I decided to give Mac
OS X a whirl.  Got one test failure:

test test_cmd_line failed -- Traceback (most recent call last):
  File "/Users/skip/src/Python-3.0/Lib/test/test_cmd_line.py", line 143, in
  test_run_code
0)
AssertionError: 1 != 0

Skip

--
messages: 76842
nosy: skip.montanaro
severity: normal
status: open
title: 3.0 test failure on Mac OS X 10.5.5

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

> (1.5802653829857376e+307+inf*j)

Those values look right;  except that there's some code near the end of 
the cexp function that's supposed to set errno to ERANGE if either the 
real or imaginary component of the result is infinity (and then math_1 
knows to raise OverflowError as a result).  It looks like that's not 
happening for some reason.

If you have time, could you try the attached patch and report what gets 
printed when cmath.exp(710+1.5j) is called?  On my machine, I get:

Python 3.1a0 (py3k:67510M, Dec  3 2008, 20:56:19) 
[GCC 4.0.1 (Apple Inc. build 5490)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import cmath
>>> cmath.exp(710.0 + 1.5j)
r.real, r.imag: 1.58027e+307, inf
Py_IS_INFINITY(r.real), Py_IS_INFINITY(r.imag): 0, 1
Traceback (most recent call last):
  File "", line 1, in 
OverflowError: math range error

Mark

--
keywords: +patch
Added file: http://bugs.python.org/file12211/cmath_debug.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Changes by Mark Dickinson <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Changes by Mark Dickinson <[EMAIL PROTECTED]>:


--
keywords: +64bit -patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Changes by Mark Dickinson <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Changes by Mark Dickinson <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4507] 3.0 test failure on Mac OS X 10.5.5

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

This looks like a duplicate of issue 4388.

--
nosy: +marketdickinson

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Changes by Mark Dickinson <[EMAIL PROTECTED]>:


___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4506] 3.0 make test failures on Solaris 10

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

Tracker issue:  I don't seem to be able to remove the 'patch' keyword
without (accidentally) ending up with something else---in this case the
64bit keyword.  Is this just me being incompetent, or should I file a
tracker bug?

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1028] Tkinter binding involving Control-spacebar raises unicode error

[Guilherme Polo]

Guilherme Polo <[EMAIL PROTECTED]> added the comment:

I've been working on a new _tkinter (named it as "plumage") these days
and I hit this same problem for trusting too much that nothing from tcl,
including tk and extensions, would give me this embedded null.

Checking another bridge to Tcl (one done for Perl) it is possible to
notice that it also chose to verify for these bytes and convert them to
something else, a 0. The code for this for Python can be found at
http://code.google.com/p/plumage/source/browse/trunk/src/utils.c#42 up
to line 76, it could/should be adapted to the _tkinter in py3k and also
for python 2.x.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4497] Compiler warnings in longobject.c

[Mark Dickinson]

Mark Dickinson <[EMAIL PROTECTED]> added the comment:

Raymond, could you please try the attached patch to see if it silences the 
compiler?

--
keywords: +patch
Added file: http://bugs.python.org/file12212/issue4497.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4508] distutils compiler not handling spaces in path to output/src files

[Brian Thorne]

New submission from Brian Thorne <[EMAIL PROTECTED]>:

I found this bug when using scipy's weave and having some inline C/C++
code. Weave uses distutils to compile the source in its own directory,
python was installed under "program files". Unfortunately it doesn't
seem to handle spaces in the path to either the output or the temporary
source files.
I checked that this was the only problem by copying the weave directory
from site-packages and put it in another directory without spaces in the
path - weave and distutils then worked fine.
I then tried the g++ command seen in the stack trace at the command line
and got the same error - so altered the command by correctly quoting the
 -c "path/to source/a.c" and the -o objects.
This worked so set out changing it in distutils.

The two files I altered were unixcompiler.py (surprising as I am under
windows!) and cygwinccompiler.py 

This was clearly an older stable build so I checked out the python trunk
r67510 on windows (32bit), made a patch, and tested with my weave
dependant code.
(I am not familiar enough with distutils to make a standalone test).

The same method to cause a problem has the same effect in ubuntu - the
build directory seems to default to users home, but as the source path
has a space in it g++ gets confused.

--
components: Distutils
files: distutils_compiler_quoting.patch
keywords: patch
messages: 76848
nosy: Thorney
severity: normal
status: open
title: distutils compiler not handling spaces in path to output/src files
type: behavior
versions: Python 2.1.1, Python 2.1.2, Python 2.2, Python 2.2.1, Python 2.2.2, 
Python 2.2.3, Python 2.3, Python 2.4, Python 2.5, Python 2.5.3, Python 2.6, 
Python 2.7, Python 3.0, Python 3.1
Added file: http://bugs.python.org/file12213/distutils_compiler_quoting.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4509] possible memoryview bug

[gumpy]

New submission from gumpy <[EMAIL PROTECTED]>:

I'm unsure of the expected behavior in this case but it seems odd. The
bytearray in the following example can be resized to a length of 5-10
bytes without throwing an exception.


Python 3.0rc3 (r30rc3:67312, Dec  3 2008, 10:38:14) 

[GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu3)] on linux2

>>> b = bytearray(b'x' * 10)

>>> v = memoryview(b)

>>> b[:] = b'y' * 11

Traceback (most recent call last):

  File "", line 1, in 

BufferError: Existing exports of data: object cannot be re-sized

>>> b[:] = b'y' * 5

>>> b

bytearray(b'y')

>>> v.tobytes()

b'y\x00'

>>> v2 = memoryview(b)

>>> v2.tobytes()

b'y'

--
components: Interpreter Core
messages: 76849
nosy: gumpy
severity: normal
status: open
title: possible memoryview bug
type: behavior
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4497] Compiler warnings in longobject.c

[Raymond Hettinger]

Raymond Hettinger <[EMAIL PROTECTED]> added the comment:

Yes, the compiler is happy now.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4384] Add a warnings.showwarning replacement for logging

[Vinay Sajip]

Vinay Sajip <[EMAIL PROTECTED]> added the comment:

Checked into trunk, r67511.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2350] 'exceptions' import fixer

[Brett Cannon]

Changes by Brett Cannon <[EMAIL PROTECTED]>:


--
resolution:  -> fixed
status: open -> closed

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4510] ValueError for list.remove() not very helpful

[Brett Cannon]

New submission from Brett Cannon <[EMAIL PROTECTED]>:

If you try to remove something from a list, e.g. ``[].remove(1)``, the
message from ValueError is rather useless: "ValueError: list.remove(x):
x not in list". It should probably list the repr for the argument to
help in debugging.

--
keywords: easy
messages: 76852
nosy: brett.cannon
priority: low
severity: normal
stage: needs patch
status: open
title: ValueError for list.remove() not very helpful
type: behavior
versions: Python 2.7, Python 3.1

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1025540] urllib2 http auth

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

this should be trivial to implement (other than urllib and urllib2 being
a giant mess).  adding to my queue.

--
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4201] Pdb cannot access source code in zipped packages.

[Alexander Belopolsky]

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:

No, I only used __main__.py to make it easy to reproduce the problem.
Pdb will not be able to access code in any module with a custom
__loader__.  For example, if you move f() to foo.py inside test.zip
and import it from __main__, you will see the same issue.  My patch
gives linecache.getlines() called by Pdb access to module's globs and
thus to its __loader__ .  It has nothing to do with runpy.

> The problem is actually with runpy not being able to set __file__
> correctly, rather than being pdb specific.

You must be thinking issue4197 where two distinct problems are
adressed:  first, the crash due to __file__ set to None by runpy and
second, missing globs parameter to linecache.getlines() in doctest
module.

My patch, doctest-1.patch works around the first issue and fixes the second.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

We need make sure this happens for 2.7/3.1.

As its large enough to be a new feature it won't make it into
2.4/2.5/2.6/3.0.

--
nosy: +gregory.p.smith
priority: normal -> high
versions: +Python 2.7, Python 3.1 -Python 2.4

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4140] urllib2: request with digest auth through proxy fail

[Gregory P. Smith]

Changes by Gregory P. Smith <[EMAIL PROTECTED]>:


--
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith
priority:  -> normal
versions: +Python 2.7, Python 3.1 -Python 2.5

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

[Senthil]

Senthil <[EMAIL PROTECTED]> added the comment:

I agree, gregory. I had verified the fix and supplied patch for py2.6
and py3K. If those still apply to the trunk, I think we should go ahead,
otherwise I shall come with the new patch for 2.7/3k.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4511] Decorators should have an index entry

[K. C. Wong]

New submission from K. C. Wong <[EMAIL PROTECTED]>:

While decorators have been introduced since Python 2.4, there continues to 
be no index reference to it in the Python Language Reference. Given this 
being a major language feature, I think it is an oversight.

--
assignee: georg.brandl
components: Documentation
messages: 76857
nosy: dvusboy, georg.brandl
severity: normal
status: open
title: Decorators should have an index entry
type: feature request
versions: Python 2.4, Python 2.5, Python 2.5.3, Python 2.6

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4201] Pdb cannot access source code in zipped packages.

[Alexander Belopolsky]

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:

Off-topic: How to report a bug tracker bug?

The e-mail I sent in response to Nick's post started with:

"""
On Wed, Dec 3, 2008 at 3:51 PM, Nick Coghlan <[EMAIL PROTECTED]> 
wrote:
> Just to confirm - this is specific to __main__.py right?
>
No, I only used __main__.py to make it easy to reproduce the problem.
...
"""

But the first two lines got eaten by the tracker.  Should I open an 
issue here and if so, what do I set as a component?

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4512] Add get_filename method to zipimport

[Alexander Belopolsky]

New submission from Alexander Belopolsky <[EMAIL PROTECTED]>:

>From issue4197:

"""
runpy needs a non-standard PEP 302 extension to set __file__ correctly
in the modules it runs. The pkgutil stuff it uses to find pure Python
modules in the filesystem supports that extension, but zipimport doesn't
(yet).
"""  -- Nick Coghlan

I am working on a patch.

--
components: Extension Modules
messages: 76859
nosy: belopolsky
severity: normal
status: open
title: Add get_filename method to zipimport
type: feature request
versions: Python 2.7

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4197] Doctest module does not work with zipped packages

[Alexander Belopolsky]

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:

I created issue4512 to implement get_filename extension in zipimport.  
Will post a patch shortly.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4512] Add get_filename method to zipimport

[Alexander Belopolsky]

Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:


--
nosy: +ncoghlan

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1581476] Text search gives bad count if called from variable trace

[Guilherme Polo]

Guilherme Polo <[EMAIL PROTECTED]> added the comment:

This is indeed a problem with Tkinter only, but I didn't check what is
causing it yet.

For the suggestion about fixing the search method regarding the pattern:
the fix is almost fine, but we need to disallow None as a pattern.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4512] Add get_filename method to zipimport

[Alexander Belopolsky]

Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:


--
keywords: +patch
Added file: http://bugs.python.org/file12214/zipimport.patch

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4513] Finish updating zip docstring

[Terry J. Reedy]

New submission from Terry J. Reedy <[EMAIL PROTECTED]>:

>>> help(zip) #3.0

class zip(object)
 |  zip(iter1 [,iter2 [...]]) --> zip object
 |  
 |  Return a zip object whose .__next__() method ... StopIteration.  

 | Works like the zip()
 |  function but consumes less memory by returning an iterator instead of
 |  a list.

The last sentence is left over from when 3.0 zip was itertools.izip.
Just delete it.

--
assignee: georg.brandl
components: Documentation
messages: 76862
nosy: georg.brandl, tjreedy
severity: normal
status: open
title: Finish updating zip docstring
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4512] Add get_filename method to zipimport

[Alexander Belopolsky]

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:

I have attached a rough patch implementing the get_filename.  I 
deliberately copied code from get_source method that finds the filename 
inside the zip archive  and simply prefixed that with the archive path.

I could not find any detailed discussion of what get_filename is 
supposed to do.  Pkgutil's get_filename is not documented and not unit-
tested. Google search revealed an old thread at 
, 
but it only says

"""

>runpy needs a get_filename() method, so it knows what to set __file__ 
too -
>currently its emulation supports that, but it isn't officially part of 
the 
>PEP
>302 API.

It sounds like maybe a new PEP is needed to document all the extensions 
to 
the importer/loader protocols.  :(
"""

I don't think a brand new PEP is needed, but an amendment to PEP 302 
would be helpful.  Nick, do you have any notes on what get_filename 
should do in various cases?

My implementation fixes one of the problems in issue4197:

$ ./python.exe testmodule.zip 
**
File "testmodule.zip/__main__.py", line ?, in __main__.c
Failed example:
'line 2'
Expected nothing
Got:
'line 2'
**
1 items had failures:
   1 of   1 in __main__.c
***Test Failed*** 1 failures.

Note that line number is still reported as '?', but there is no crash.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4303] [2.5 regression] ctypes fails to build on arm-linux-gnu

[Barry A. Warsaw]

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:


--
priority: deferred blocker -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue1683] Thread local storage and PyGILState_* mucked up by os.fork()

[Barry A. Warsaw]

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:


--
priority: deferred blocker -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4469] CVE-2008-5031 multiple integer overflows

[Barry A. Warsaw]

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>:


--
priority: deferred blocker -> release blocker

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4514] test_binascii is failing

[Raymond Hettinger]

New submission from Raymond Hettinger <[EMAIL PROTECTED]>:

test_binascii.py fails because crc32 accepts a string.

>From my WindowsXP box:

C:\Python30>python \python30\lib\test\test_binascii.py
test_base64invalid (__main__.BinASCIITest) ... ok
test_base64valid (__main__.BinASCIITest) ... ok
test_crc32 (__main__.BinASCIITest) ... ok
test_empty_string (__main__.BinASCIITest) ... ok
test_exceptions (__main__.BinASCIITest) ... ok
test_functions (__main__.BinASCIITest) ... ok
test_hex (__main__.BinASCIITest) ... ok
test_no_binary_strings (__main__.BinASCIITest) ... FAIL
test_qp (__main__.BinASCIITest) ... ok
test_uu (__main__.BinASCIITest) ... ok

==
FAIL: test_no_binary_strings (__main__.BinASCIITest)
--
Traceback (most recent call last):
  File "\python30\lib\test\test_binascii.py", line 177, in
test_no_binary_strings
self.assertRaises(TypeError, f, "test")
AssertionError: TypeError not raised by crc32

--
Ran 10 tests in 0.016s

FAILED (failures=1)
Traceback (most recent call last):
  File "\python30\lib\test\test_binascii.py", line 183, in 
test_main()
  File "\python30\lib\test\test_binascii.py", line 180, in test_main
support.run_unittest(BinASCIITest)
  File "C:\Python30\lib\test\support.py", line 698, in run_unittest
_run_suite(suite)
  File "C:\Python30\lib\test\support.py", line 681, in _run_suite
raise TestFailed(err)
test.support.TestFailed: Traceback (most recent call last):
  File "\python30\lib\test\test_binascii.py", line 177, in
test_no_binary_strings
self.assertRaises(TypeError, f, "test")
AssertionError: TypeError not raised by crc32

--
assignee: loewis
components: Extension Modules
messages: 76864
nosy: loewis, rhettinger
severity: normal
status: open
title: test_binascii is failing
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4515] Formatting error in "What's New in Python 3.0"

[Peter Wang]

New submission from Peter Wang <[EMAIL PROTECTED]>:

In the section "Removed Syntax", there is some ReST markup that leaked
through into the output:

"The only acceptable syntax for relative imports is from .``[*module*]
:keyword:`import` *name*; :keyword:`import` forms not starting with ``.
are always interpreted as absolute imports. (PEP 0328)"

--
assignee: georg.brandl
components: Documentation
messages: 76865
nosy: georg.brandl, pwang
severity: normal
status: open
title: Formatting error in "What's New in Python 3.0"
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4516] Another formatting error in "What's New in Python 3.0"

[Peter Wang]

New submission from Peter Wang <[EMAIL PROTECTED]>:

In the "Library Changes" section, the next to last bullet point about
string.letters has leaked through some ReST markup into the final
output: ":data:string.letters`"

--
assignee: georg.brandl
components: Documentation
messages: 76866
nosy: georg.brandl, pwang
severity: normal
status: open
title: Another formatting error in "What's New in Python 3.0"
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4517] improve __getattribute__ documentation

[David W. Lambert]

New submission from David W. Lambert <[EMAIL PROTECTED]>:

http://docs.python.org/dev/3.0/reference/datamodel.html#special-lookup

(After fixing the link to http://docs.python.org/3.0 at 
http://www.python.org/doc/ (and likewise the 
http://docs.python.org/whatsnew/3.0.html link.)...

The comment that __getattribute__ is "Called unconditionally to 
implement attribute accesses for instances of the class" gave me hope 
that some combination of "meta" "super" and "sub" might let me access 
__getattribute__ for expression eval('obj + another_object') despite the 
special notes.  I realize now the truth is that

"__getattribute__ is NEVER accessible in pure python code when the code 
uses the syntax of a unary or binary operator such as a+b, ~a, len(a)."
See most of the functions in this manual section.
Also name hash, which doesn't find much explicit use but could well be 
the most used python functionality.  Find a smooth way to replace my 
NEVER since code can obviously access __getattribute__ from the special 
function.

Thank you, and great work!

--
assignee: georg.brandl
components: Documentation
messages: 76867
nosy: LambertDW, georg.brandl
severity: normal
status: open
title: improve __getattribute__ documentation
type: feature request
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4517] improve __getattribute__ documentation

[David W. Lambert]

David W. Lambert <[EMAIL PROTECTED]> added the comment:

>>> class c:
...  def __getattribute__(self,*args):
...   print('getattribute chimes in')
... 

>>> c()+3
Traceback (most recent call last):
  File "", line 1, in 
TypeError: unsupported operand type(s) for +: 'c' and 'int'

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4518] broken link to python 3 doc on main doc page

[Bernard Gray]

New submission from Bernard Gray <[EMAIL PROTECTED]>:

http://www.python.org/doc/

The "Python 3.0" link in the doc section is broken:

Python 3.0 documentation is also available:

* What's new in Python 3.0
* Python 3.0

It points to: http://docs.python.org/3.0
which gives a 404

--
assignee: georg.brandl
components: Documentation
messages: 76869
nosy: cleary, georg.brandl
severity: normal
status: open
title: broken link to python 3 doc on main doc page
type: behavior
versions: Python 3.0

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4518] broken link to python 3 doc on main doc page

[David W. Lambert]

David W. Lambert <[EMAIL PROTECTED]> added the comment:

Meanwhile, use

http://docs.python.org/dev/3.0/

--
nosy: +LambertDW

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4518] broken link to python 3 doc on main doc page

[David W. Lambert]

Changes by David W. Lambert <[EMAIL PROTECTED]>:


--
nosy:  -LambertDW

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4082] __main__.__file__ not set correctly when -m switch gets __main__ from a zipfile

[Alexander Belopolsky]

Changes by Alexander Belopolsky <[EMAIL PROTECTED]>:


--
nosy: +belopolsky

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4082] __main__.__file__ not set correctly when -m switch gets __main__ from a zipfile

[Alexander Belopolsky]

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:

See issue4512

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4197] Doctest module does not work with zipped packages

[Alexander Belopolsky]

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment:

While the patch at issue4512 fixes the crash, it does not fix the line 
number issue.  I would prefer to start with doctest-1.patch like solution 
because changing the PEP 302 loader protocol by adding get_filename needs 
additional discussion and certainly is not a candidate for 2.5.x or 2.6.x 
bug fix releases.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4483] Error to build _dbm module during make

[Leger]

Leger <[EMAIL PROTECTED]> added the comment:

I install the Python3.0 (final), the test make is the same and the
result too. I join the output.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue4514] test_binascii is failing

[Martin v. Löwis]

Martin v. Löwis <[EMAIL PROTECTED]> added the comment:

The problem is that the Windows implementation of crc32 is different
from the Unix implementation, and that implementation was missed in
r67472. The fix should be fairly trivial.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com