[issue3041] autodoc does not support unicode docstrings

New submission from Christophe de Vienne <[EMAIL PROTECTED]>: If I define unicode docstrings in my python source, autodoc crash because it tries to decode them, which force a ascii encode first. A trivial patch fix the issue : Index: sphinx/ext/autodoc.py ===

[issue3039] tarfile.TarFileCompat.writestr(ZipInfo, str) raises AttributeError

Changes by Lars Gustäbel <[EMAIL PROTECTED]>: -- assignee: -> lars.gustaebel nosy: +lars.gustaebel ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3042] Add PEP 8 compliant aliases to threading module

New submission from Nick Coghlan <[EMAIL PROTECTED]>: PEP 371 highlighted the non-PEP 8 compliant nature of the threading API. Since part of that PEP involves updating the multiprocessing API to be PEP 8 compliant before addition the standard library, the threading API should also be updated to b

[issue643841] New class special method lookup change

Nick Coghlan <[EMAIL PROTECTED]> added the comment: I've attached the latest version of the module as an actual patch against Python SVN. It differs slightly from the last version uploaded as separate files, in that in-place operations on a proxied object will no longer strip the proxy wrapper o

[issue643841] New class special method lookup change

Nick Coghlan <[EMAIL PROTECTED]> added the comment: Note that I'll be offline for the next few days, so I want be able to respond to any comments until some time next week. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3004] Bug in slice.indices()

Mark Dickinson <[EMAIL PROTECTED]> added the comment: I agree that those -1s should really be 0s. Do you have any examples of real-life code that's affected by this bug? It doesn't seem like something that would be a problem in practice. -- nosy: +marketdickinson priority: -> normal

[issue3042] Add PEP 8 compliant aliases to threading module

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Is this what you were looking for? (in the patch) What I did could also be done with metaclasses, but I thought that would be overkill. Warning: this patch causes test threading to crash when run with the -3 flag. -- keywords: +pat

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

Peter N <[EMAIL PROTECTED]> added the comment: Martin, On solaris 10 x86, this patch makes it possible to build python 2.5.x. Without it, there is no way for the automated build to work. I believe that your characterization of it as "Therefore, I claim that this makes things more complex, and do

[issue3042] Add PEP 8 compliant aliases to threading module

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Attaching a patch which fixes everything. Added file: http://bugs.python.org/file10523/new_threading_api2.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue3038] Return results from Python callbacks to Tcl as Tcl objects, please backport it.

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> loewis nosy: +loewis ___ Python tracker <[EMAIL PROTECTED]> ___ ___ P

[issue3041] autodoc does not support unicode docstrings

Georg Brandl <[EMAIL PROTECTED]> added the comment: Thanks, fixed in r63958. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue643841] New class special method lookup change

Adam Olsen <[EMAIL PROTECTED]> added the comment: The inplace operators aren't right for weakref proxies. If a new object is returned there likely won't be another reference to it and the weakref will promptly be cleared. This could be fixed with another property like _target, which by default

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > So, since this patch allows python to be built 64-bit on a biarch > system, and without it, the build doesn't work This is simply not true. I can build Python 2.5 just fine for 64-bit SPARC, using gcc, with CC="gcc -m64" ./configure make

[issue2799] Remove PyUnicode_AsString(), rework PyUnicode_AsStringAndSize(), add PyUnicode_AsChar()

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: I now think the proposed changes wouldn't be bad thing, after all. I have been bitten myself by the confusing naming of the Unicode API. So, there is definitely a potential for errors. The main problem with PyUnicode_AsString(), as Mar

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Your method is just flat wrong - equivalent to using a sledgehammer. The > libraries fail to link not because gcc install is wrong but because the > -m64 flag needs to be passed to the linker. And indeed, the flag *is* passed to the link

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

Bob Atkins <[EMAIL PROTECTED]> added the comment: Martin, Your method is just flat wrong - equivalent to using a sledgehammer. The libraries fail to link not because gcc install is wrong but because the -m64 flag needs to be passed to the linker. Your method just fixes the compilation stage.

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Just to demonstrate there is really a problem with the gcc installation (gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)), here is the linker line: gcc -m64 -shared build/temp.solaris-2.10-sun4u-2.5/net/tb0/home/loewis/25/Modules/_struct

[issue1628484] Python 2.5 64 bit compile fails on Solaris 10/gcc 4.1.1

Bob Atkins <[EMAIL PROTECTED]> added the comment: I rest my case - you found /_*one*_/ of the problems which you are blaming on gcc but in fact is not gcc's fault. You /_*must*_/ specify the correct -L and -R paths to the various alternate 64 bit libs. Don't expect the compiler to figure it ou

=?utf-8?q?[issue2799]_Remove_PyUnicode=5FAsString(), =09rework_PyUnicode=5FAsStringAndSize(), _add_PyUnicode=5FAsChar()?=

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-06-05 21:14, Alexandre Vassalotti wrote: > Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: > > I now think the proposed changes wouldn't be bad thing, after all. I > have been bitten myself by the confusing naming of t

[issue2799] Remove PyUnicode_AsString(), rework PyUnicode_AsStringAndSize(), add PyUnicode_AsChar()

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > How about PyUnicode_GetUTF8Buffer() or just PyUnicode_UTF8() ?! -1 > Note that the function *must* check the UTF-8 buffer for embedded > NUL bytes and then raise an exception if it finds one. Otherwise, > the API would silently cause trun

[issue3043] Recursion bug in deepcopy

New submission from Tyler Laing <[EMAIL PROTECTED]>: With the following code: class Vertex: def __init__(self, type): self.type = type self.color=-1 self.edges=[] class Edge: def __init__(self, V1, V2):

[issue2799] Remove PyUnicode_AsString(), rework PyUnicode_AsStringAndSize(), add PyUnicode_AsChar()

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-06-05 22:50, Martin v. Löwis wrote: >> Note that the function *must* check the UTF-8 buffer for embedded >> NUL bytes and then raise an exception if it finds one. Otherwise, >> the API would silently cause truncations. > > PyStrin

[issue3043] Recursion bug in deepcopy

Tyler Laing <[EMAIL PROTECTED]> added the comment: Whoops, sorry, correction, when there are 100 vertexes and 500 edges. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3043] Recursion bug in deepcopy

Guilherme Polo <[EMAIL PROTECTED]> added the comment: This should have been fixed at 2.2, as long as you change your classes to new-style classes. If it still happens, post a sample code using your new code that uses new-style classes. -- nosy: +gpolo ___

[issue3043] Recursion bug in deepcopy

Tyler Laing <[EMAIL PROTECTED]> added the comment: Same problem, even with new-style classes. Here, I'll show the function I use to generate the graph as well. class Vertex(object): def __init__(self, type): self.type = type self.color=-1 s

[issue3004] Bug in slice.indices()

Arnaud Bergeron <[EMAIL PROTECTED]> added the comment: It's for code that I am developping. I developped a class to allow full slicing over iterators (like what islice does, but with negative indexes). When I have a positive step I just foward the call to isclice using slice.indices() to comput

[issue3044] Simplify the Integral ABC

New submission from Raymond Hettinger <[EMAIL PROTECTED]>: See attached patches. The PEP is also updated for Exact/Inexact which were removed a good while ago. -- assignee: gvanrossum components: Library (Lib) files: numbers.diff keywords: patch messages: 67734 nosy: gvanrossum, rhettin

[issue3044] Simplify the Integral ABC

Changes by Raymond Hettinger <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10529/pep.diff ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3044] Simplify the Integral ABC

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Looks like you accidentally removed 2-arg __pow__ from the Complex ABC. This should stay of course. Also, please add the binary operators back in a new ABC called Binary deriving from Integral. ___ Pyth

[issue2582] Unpickling of range objects fail in Py3k

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: Weird. I wonder why it succeeds to pickle to range object at all. It seems the __reduce_ex__ method emits bogus value. >>> r.__reduce_ex__(2) (, (,), None, None, None) Anyway, that is easy to fix when you know the trick. So, here i

[issue2582] Unpickling of range objects fail in Py3k

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: Oh, here is a slightly more efficient version. Added file: http://bugs.python.org/file10531/fix_range_pickling-2.patch ___ Python tracker <[EMAIL PROTECTED]> __

[issue3044] Simplify the Integral ABC

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: Apologies. Didn't know you wanted to go that direction. Will leave this for someone who wants to expand numbers.py rather than simplifying it. -- resolution: -> rejected status: open -> closed __

[issue2582] Unpickling of range objects fail in Py3k

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: xrange() in Python 2.x is also affected by this bug. So, here is the fix. -- versions: +Python 2.5, Python 2.6 Added file: http://bugs.python.org/file10532/fix_xrange_pickling.patch ___ Pytho

[issue3044] Simplify the Integral ABC

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Excuse me? Have you actually been following the thread? ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3008] Let bin() show floats

Alexandre Vassalotti <[EMAIL PROTECTED]> added the comment: Kind of a cool hack. I am not sure how useful it is though. Personally, I find ``struct.pack('d', f)`` slightly more educative (more useful too), but that is just me. And if you allow bin() to accept floats, will you make Python accept

[issue3042] Add PEP 8 compliant aliases to threading module

Nick Coghlan <[EMAIL PROTECTED]> added the comment: The code changes in the patch look pretty good to me (although you probably want to actually use @wraps inside _old_api!) There are obviously also documentation and test suite changes that will be needed. __

[issue643841] New class special method lookup change

Nick Coghlan <[EMAIL PROTECTED]> added the comment: Ah, that would answer my #XXX comment regarding that in the patch. Agreed, the best answer will be to factor out the _rewrap operation into a new class method. (Next week though...) ___ Python tracker <[EMAIL

[issue3042] Add PEP 8 compliant aliases to threading module

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: On Thu, Jun 5, 2008 at 8:56 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > Nick Coghlan <[EMAIL PROTECTED]> added the comment: > > The code changes in the patch look pretty good to me (although you > probably want to actually use @wraps in

[issue3042] Add PEP 8 compliant aliases to threading module

Changes by Adam Olsen <[EMAIL PROTECTED]>: -- nosy: +Rhamphoryncus ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list maili

[issue3045] Windows online help broken when spaces in TEMP environ

New submission from Peter Whaite <[EMAIL PROTECTED]>: If the environ vars TEMP or TMP contain spaces on w32 the on-line help will not work. e.g. help('or') gives the message The system cannot find the file specified. This is because pydoc.tempfilepager sets filename=tempfile.mktemp() which

[issue3046] Locking should be removed from the new buffer protocol

New submission from Stefan Behnel <[EMAIL PROTECTED]>: Here is a patch against the current PEP 3118 that removes the LOCK flag. It follows this discussion on the Py3k mailing list: http://comments.gmane.org/gmane.comp.python.python-3000.devel/13409?set_lines=10 It has not yet been approved