[issue8481] doc: ctypes no need to explicitly allocate writable memory with Structure

New submission from anatoly techtonik : ctypes docs should mention that Structures can be passed with byref() to functions expecting pointer to mutable memory without explicit allocation of mutable memory block with create_string_buffer() or similar function. -- assignee: georg.brandl

[issue4256] optparse: provide a simple way to get a programmatically useful list of options

Andy Buckley added the comment: > The backward compatible solution is to have --help-options disabled by > default, and ask people to enable it with add_interface=True. Or to add the option just before arg parsing, if it has not already been defined? Thanks for the patches, Filip! Andy ---

[issue8469] struct - please make sizes explicit

Mads Kiilerich added the comment: The more times I read the documentation and your comments I can see that the implementation is OK and the documentation is "complete" and can be read correctly. Please take this as constructive feedback to improving the documentation to make it easier to unde

[issue8469] struct - please make sizes explicit

Mark Dickinson added the comment: Thanks for the doc suggestions. Actually, the current docs were revised recently; this issue is a helpful reminder to me that those doc revisions need to be backported. :) If you want to see the current docs, look at: http://docs.python.org/dev/library/str

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

New submission from Nick Coghlan : Remaining failure after resolution of issue8437: == FAIL: test_basic_command (test.test_gdb.PyBtTests) Verify that the "py-bt" command works

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: And Dave's comment from the other issue: Reading the frame information seems to be highly sensitive to the optimization level and the exact version of gcc for the build, and the exact version of gdb, alas. I've been tracking a failure like the one you describe

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: Potentially relevant gcc and gdb version info: ~$ gcc --version gcc (Ubuntu 4.4.1-4ubuntu9) 4.4.1 Copyright (C) 2009 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY

[issue8437] test_gdb: gdb.Frame has no attribute function

Nick Coghlan added the comment: Remaining problem recorded as issue 8482 -- components: +Library (Lib), Tests keywords: +64bit -patch versions: +Python 2.7 ___ Python tracker ___

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

Charles-Francois Natali added the comment: > And that report shows only a single thread, so I have to assume that the 8MB figure applies there. > Nevertheless, we can remove the stack buffer since it's probably useless. It just seems unlikely to me to be the root cause of the stack overflow. I

[issue6600] MemoryError in AiX 64-bit - PyMem_MALLOC fails in open/fdopen

Antoine Pitrou added the comment: Ok, closing then. -- resolution: -> works for me status: open -> closed ___ Python tracker ___ ___

[issue8437] test_gdb: gdb.Frame has no attribute function

Nick Coghlan added the comment: (Oops, thought I had reverted those accidental edits by reloading the page. I guess not) -- keywords: +patch -64bit ___ Python tracker ___ __

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

STINNER Victor added the comment: Readable version of the error message (with newlines): - AssertionError: 'Breakpoint 1 at 0x453510: file Objects/object.c, line 330. [Thread debugging using libthread_db enabled] Breakpoint 1, PyObject_Print (op=42, fp=0x77532780, flags=1) at Ob

[issue8483] asyncore.dispatcher.__repr__() is weird

New submission from Dirkjan Ochtman : This is rather confusing: Python 2.6.4 (r264:75706, Mar 8 2010, 08:41:55) [GCC 4.3.4] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import socket, asyncore >>> class T: ... pass ... >>> t = T() >>> print t <__main_

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

Matthias Klose added the comment: > That would explain why it's only reported on Ubuntu the original report is from the rPath distribution. -- ___ Python tracker ___ ___

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: Thanks Victor. The test actually runs fine under "./configure --with-pydebug", but reverting to a plain "./configure" and rebuilding means I get the error again. Definitely sounds like it could be due to the compiler failing to make some relevant info availabl

[issue8483] asyncore.dispatcher.__repr__() is weird

Changes by Dirkjan Ochtman : -- nosy: +josiah.carlson, josiahcarlson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

Charles-Francois Natali added the comment: > the original report is from the rPath distribution. Never heard of this one, but http://wiki.rpath.com/wiki/rPath_Linux:rPath_Linux_2 states: Compile with --fstack-protectorand FORTIFY_SOURCE=2 (override in your recipes by modifying the securityfl

[issue8410] Fix emulated lock to be 'fair'

David Beazley added the comment: I know that multicore processors are all the rage right now, but one thing that concerns me about this patch is its effect on single-core systems. If you apply this on a single-CPU, are threads just going to sit there and thrash as they rapidly context switch

[issue8483] asyncore.dispatcher.__repr__() is weird

Dirkjan Ochtman added the comment: Current guess for this behavior: dispatcher doesn't have __str__, so __getattr__ escalates to _socket.socket.__str__, which gets redirected to _socket.socket.__repr__. -- ___ Python tracker

[issue8451] syslog.syslog('msg') logs message with ident "python".

R. David Murray added the comment: One argument in favor of letting openlog pick it (assuming it uses argv[0]) is that for a while at least we will have many systems running both python2 and python3, and it might be useful to have that distinction show up in the log if the fallback is used.

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

New submission from Beda Kosata : When trying a secure connection to an HTTPS server with server certificate verification, I get very strange behaviour when the digest used in the signing certificate is SHA-256 (+RSA). On Windows with Python 2.6.4 or 2.6.5, I consistently get the following erro

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Changes by Beda Kosata : Added file: http://bugs.python.org/file17022/chain.pem ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

STINNER Victor added the comment: > The test actually runs fine under "./configure --with-pydebug" (...) I changed configure to disable all compiler optimisations if --with-pydebug is used. Retry with ./configure CFLAGS="-O0". A variable may be optimized (use a register instead a variable all

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Changes by Antoine Pitrou : -- nosy: +giampaolo.rodola, janssen, pitrou priority: -> normal type: crash -> behavior versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker _

[issue4256] optparse: provide a simple way to get a programmatically useful list of options

R. David Murray added the comment: I prefer an approach that allows this option to be defined by default, since if it is not defined by default it defeats part of the purpose of having the option. The program author may not be concerned with completions (or even know about them), but if the

[issue4256] optparse: provide a simple way to get a programmatically useful list of options

R. David Murray added the comment: Removing 2.7 since it is now in feature freeze. -- versions: -Python 2.7 ___ Python tracker ___ __

[issue8483] asyncore.dispatcher.__repr__() is weird

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Antoine Pitrou added the comment: Changing OpenSSL initialization to the following seems to fix the issue (with OpenSSL 0.9.8k and 1.0.0): /* Init OpenSSL */ SSL_load_error_strings(); SSL_library_init(); #ifdef WITH_THREAD /* note that this will start threading

[issue7384] curses crash on FreeBSD

Stefan Krah added the comment: Jeroen, thanks for the idea. I asked Thomas Dickey and he said that one should not load both libncurses.so and libncursesw.so. I think this means that if libreadline.so is already linked against libncurses.so, we are stuck with libncurses.so for the curses module.

[issue8485] Don't accept bytearray as filenames, or simplify the API

New submission from STINNER Victor : r72313 (PEP 383) created the PyUnicode_FSConverter() function: encode an object to a byte string using the default file system encoding. PyBytes and PyByteArray are leaved unchanged (just increment the reference counter), PyUnicode is encoded to PyBytes (if

[issue8485] Don't accept bytearray as filenames, or simplify the API

Changes by STINNER Victor : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8480] test_gdb: No frame is currently selected.

STINNER Victor added the comment: I may be related to #8482 (compiler optimization level?). -- nosy: +haypo ___ Python tracker ___ ___

[issue8479] test_gdb: No stack

STINNER Victor added the comment: I may be related to #8482 (compiler optimization level?). -- nosy: +haypo ___ Python tracker ___ ___

[issue8485] Don't accept bytearray as filenames, or simplify the API

STINNER Victor added the comment: Patch removing bytearray filename support: it mostly removes code. -- keywords: +patch Added file: http://bugs.python.org/file17024/no_bytearray_filename.patch ___ Python tracker _

[issue8485] Don't accept bytearray as filenames, or simplify the API

Antoine Pitrou added the comment: Or perhaps the bytearray can be converted to a bytes object. This is not optimal performance-wise but is unlikely to make a difference in real-world code (if you are passing a filename to an external API, chances are some IO will occur which will dwarf the co

[issue8483] asyncore.dispatcher.__repr__() is weird

R. David Murray added the comment: I'm not clear on what you are finding weird, here. Your issue title talks about __repr__, but your last post talks about __str__. -- nosy: +r.david.murray priority: -> low ___ Python tracker

[issue8486] [PATCH] threading.Event()

New submission from Benjamin VENELLE : Hi, I'm suggesting to declare a __bool__() function as an alias for is_set() in Event class from threading package. So Event objects could be used like booleans. Ex: I thought 'while(not event): do_something()' is much intuitive than 'while(not event.i

[issue8483] asyncore.dispatcher.__repr__() is weird

Dirkjan Ochtman added the comment: David, just have a look at the interpreter transcript, in particular the results of the print statements. I'm not sure why it happens, in my previous message I just stated a hypothesis. -- ___ Python tracker

[issue8486] [PATCH] threading.Event()

Antoine Pitrou added the comment: Due to the nature of an Event, you should in most situations wait() on it, rather than test its value. Also, changing the boolean value of an Event would break existing code. I therefore think this should be rejected. -- nosy: +pitrou ___

[issue7384] curses crash on FreeBSD

Mark Dickinson added the comment: This patch looks good to me, assuming that the buildbots are happy. I agree that this seems like a sensible solution for now, even if it means limiting users to ncurses rather than ncursesw. I was initially a bit surprised that it works on OS X, since OS X d

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: I'll weight for Dave to weigh in before I dig any further - the problem I am seeing seems to have a lot in common with the issue he reported on 64-bit Fedora, but I only followed about half of that bug discussion. -- ___

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Changes by Nick Coghlan : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opti

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Nick Coghlan added the comment: I'll wait for Dave to weigh in before I dig any further - the problem I am seeing seems to have a lot in common with the issue he reported on 64-bit Fedora, but I only followed about half of that bug discussion. -- _

[issue8486] [PATCH] threading.Event()

Benjamin VENELLE added the comment: Yes, I agree when Event objects are used to sync threads. But in my case, I'm using them like signals to terminate some server's thread through a proper way. This is a just a "cosmetic" stuff to enhance readability. -- _

[issue8486] [PATCH] threading.Event()

Antoine Pitrou added the comment: > Yes, I agree when Event objects are used to sync threads. But in my > case, I'm using them like signals to terminate some server's thread > through a proper way. In this case, you don't have to use an Event. A boolean attribute on one of your objects is enoug

[issue8188] Unified hash for numeric types.

Mark Dickinson added the comment: > Regarding a hash function for complex types, I think documenting the > existing behavior for PyComplex is sufficient. The magic number 103 > > could be documented in hash_info as 'multiplier' and _PyHASH_MULTIPLIER. Seems reasonable; I'm tempted to ca

[issue8486] [PATCH] threading.Event()

Benjamin VENELLE added the comment: > In this case, you don't have to use an Event. A boolean attribute on one > of your objects is enough. > (similarly, you would use a "volatile" variable in C) This is already the case with Event. Look at threading.py @line ~355 Event class has a kinda priva

[issue8480] test_gdb: No frame is currently selected.

STINNER Victor added the comment: libpython.py had a type "PyStringObjectPtr" referencing "PyStringObject" type, whereas Python3 uses "PybytesObject". That's why you got this error. It should be fixed by r80311 (and r80312). -- resolution: -> fixed status: open -> closed ___

[issue8479] test_gdb in Python3: No stack

STINNER Victor added the comment: The problem is that test_gdb is not compatible with Python3. test_gdb uses "print x" syntax instead of "print(x)", and "except XXX, xxx:" instead of "except XXX as xxx:". Note: "print range(1000)" => "print(list(range(1000)))". DebuggerOutput.run_gdb() shoul

[issue8486] threading.Event()

Antoine Pitrou added the comment: > Using a boolean would look almostly the same so why to reinvent the > wheel ? :) Hmm, /you/ are reinventing the wheel by suggesting to use an Event instead of a simple boolean. Just loop like this: while not self.stop_me: # etc. and set the stop_me attri

[issue7755] copyright clarification for audiotest.au

VanL added the comment: However, a 3 second clip used for testing purposes in an open source programming language appears to meet the guidelines for fair use in the United States. In particular, no one is going to use the test clip as a substitute for any part of the Monty Python skit. There

[issue7755] copyright clarification for audiotest.au

Antoine Pitrou added the comment: Shouldn't "My hovercraft is full of eels" be considered an original creation of the Monty Python, and as such copyrighted? -- nosy: +pitrou ___ Python tracker

[issue7755] copyright clarification for audiotest.au

Barry A. Warsaw added the comment: Note that guido.au is just him saying some crazy sh*t and I'm fairly certain couldn't be construed as copyrighted material (unless Guido is going to assert copyright over it :) -- ___ Python tracker

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Antoine Pitrou added the comment: Here is a patch. I'm not really happy about the test because it relies on an external test site, and the certificate apparently expires in 2011. -- keywords: +patch Added file: http://bugs.python.org/file17025/algos.patch _

[issue8479] test_gdb in Python3: No stack

Dave Malcolm added the comment: Issue 8380 contains a port of the code and tests to python 3; it's awaiting review. -- superseder: -> Port of the gdb7 debugging hooks to the "py3k" branch ___ Python tracker _

[issue8479] test_gdb in Python3: No stack

Changes by Dave Malcolm : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8480] test_gdb: No frame is currently selected.

Dave Malcolm added the comment: There was a patch for this attached to issue 8380, and you've fixed things in a different way. Should I regenerate a patch against what's now in SVN, or should we use my patch? -- assignee: dmalcolm -> loewis ___ Py

[issue5516] equality not symmetric for subclasses of datetime.date and datetime.datetime

Alexander Belopolsky added the comment: There is another inconsistency that this patch does not seem to cure. With patch applied and D and DT defined as in OP, >>> D(1900,1,1) > DT(1900,1,1) True but >>> DT(1900,1,1) < D(1900,1,1) Traceback (most recent call last): File "", line 1, in Ty

[issue8380] Port of the gdb7 debugging hooks to the "py3k" branch

Dave Malcolm added the comment: Looking at issue 8480, it looks like this a partial fix was applied, which will mean this patch will no longer apply. Should I regenerate a patch against what's now in SVN, or should we use my patch? -- ___ Python t

[issue8380] Port of the gdb7 debugging hooks to the "py3k" branch

Changes by Dave Malcolm : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue8451] syslog.syslog('msg') logs message with ident "python".

Eric Smith added the comment: I have the same reasoning as David, although I was thinking about python vs. pythonw. But it's not a big deal. I think you should check it in as-is, and we can worry about modifying it later, if need be. -- ___ Python

[issue8483] asyncore.dispatcher.__repr__() is weird

Giampaolo Rodola' added the comment: I think the problem relies in here: # cheap inheritance, used to pass all other attribute # references to the underlying socket object. def __getattr__(self, attr): return getattr(self.socket, attr) I wonder why this has been added in th

[issue8380] Port of the gdb7 debugging hooks to the "py3k" branch

STINNER Victor added the comment: > Looking at issue 8480, it looks like this a partial fix was applied, Martin fixed calls to assertListing(). I renamed PyStringObjectStr to PyBytesStringPtr and used a breakpoint on textiowrapper_write() instead of PyObject_Dump(). Your patch uses a breakpoi

[issue8380] Port of the gdb7 debugging hooks to the "py3k" branch

Dave Malcolm added the comment: Thanks; I'm working on a newer version of the patch based on what's in SVN. I prefer your choice of breakpoint, and I've changed my mind about the python2 vs python3 proxyval handling. Hope to have a fresh patch later today. -- _

[issue8487] os.mknod() fails on NFS mounted directories

New submission from Nikolaus Rath : $ cat test.py #!/usr/bin/env python import os import stat dbfile = './testfile.test' with open(dbfile, 'w') as fh: print('Opened file for writing') os.unlink(dbfile) os.mknod(dbfile, stat.S_IRUSR | stat.S_IWUSR | stat.S_IFREG) print('Mknod\'ed file') [cl..

[issue8483] asyncore.dispatcher.__repr__() is weird

R. David Murray added the comment: I somehow missed the fact that B was a dispatcher subclass. Too early in my morning, I guess. So, I think the title of this issue should be "asyncore.dispatcher's __repr__ not being used as fallback for __str__", and your speculation looks likely to be on

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Antoine Pitrou added the comment: After several attempts, I've failed generating a self-signed certificate that would reproduce the issue without relying on an external server. Perhaps there's something else than simply the hashing algorithm. In any case I think I'm simply gonna keep the curr

[issue8486] threading.Event()

R. David Murray added the comment: This is a duplicate of #5998, which was rejected. -- nosy: +r.david.murray priority: -> normal resolution: -> rejected stage: -> committed/rejected status: open -> closed superseder: -> Add __bool__ to threading.Event and multiprocessing.Event ___

[issue5516] equality not symmetric for subclasses of datetime.date and datetime.datetime

Alexander Belopolsky added the comment: Upon further reflection I am -1 on this patch. First, as implemented this patch changes behavior of an explicit invocation of date.__eq__. The patch proposes to remove the following tests: -# Neverthelss, comparison should work with the base-c

[issue5516] equality not symmetric for subclasses of datetime.date and datetime.datetime

Changes by Antoine Pitrou : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue8487] os.mknod() fails on NFS mounted directories

Antoine Pitrou added the comment: Well, this looks like a filesystem problem more than a Python problem. The error (errno 2) comes from the mknod() system call itself. -- nosy: +pitrou ___ Python tracker __

[issue8487] os.mknod() fails on NFS mounted directories

Changes by Antoine Pitrou : -- nosy: +exarkun ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue8483] asyncore.dispatcher.__repr__() is weird

Giampaolo Rodola' added the comment: > Unfortunately, even if forwarding everything to the socket is > questionable, it would probably be a really bad idea to change it, > since there is likely code in the field depending on this behavior. I agree, even if it would break a code which is funda

[issue8478] tokenize.untokenize first token missing failure case

Changes by rb : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mai

[issue2706] datetime: define division timedelta/timedelta

Alexander Belopolsky added the comment: Can someone (Mark?) add an acknowledgment for Victor Stinner to the NEWS file? My py3k patch was 90% code from Victor's trunk patch. -- ___ Python tracker _

[issue1673409] datetime module missing some important methods

Alexander Belopolsky added the comment: With issue2706 accepted, I think this issue can now be rejected because proposed td.tosecs() can now be spelled simply as td/timedelta(seconds=1). The other RFE for a totimestamp() method is a duplicate of issue2736. -- nosy: +Alexander.Belopols

[issue4256] optparse: provide a simple way to get a programmatically useful list of options

Steven Bethard added the comment: On Wed, Apr 21, 2010 at 12:36 AM, Andy Buckley wrote: > Or to add the option just before arg parsing, if it has not already been > defined? Something like this was suggested before and it doesn't really work out well. It means the first time you call .parse_a

[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects

R. David Murray added the comment: Well, the attribute error message could be fixed, too, by enclosing the forwarding getattr in a try/except and generating the "correct" attribute error text. Changing the forwarding behavior itself is the kind of issue that would need to be discussed on pyt

[issue8487] os.mknod() fails on NFS mounted directories

Charles-Francois Natali added the comment: > Well, this looks like a filesystem problem more than a Python problem. The error (errno 2) comes from the mknod() system call itself. Definitely. @Nikratio Just to be sure, could you provide the result of: - strace ~/tmp/test.py from NFS-mounted dir

[issue2706] datetime: define division timedelta/timedelta

Mark Dickinson added the comment: Ah, yes. Sorry, Victor! There's actually no acknowledgement in Misc/NEWS: it's not *that* common to put acknowledgements there, and I'm not sure it's necessary here, but I've fixed the commit message. -- ___ Pyt

[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects

R. David Murray added the comment: By the way, the __getattr_ was in the very first version of the code checked in to the repository. I think the chances of removing it are pretty much zero :) -- ___ Python tracker

[issue1673409] datetime module missing some important methods

Mark Dickinson added the comment: Closing this as a duplicate of issue 2736, as suggested. I'll combine the nosy lists. (BTW, as well as the newly introduced division methods, td.tosecs already exists, except that it's spelt td.total_seconds.) -- resolution: -> duplicate status: op

[issue2736] datetime needs an "epoch" method

Mark Dickinson added the comment: Close issue 1673409 as a duplicate of this one; combining nosy lists. -- nosy: +catlee, erik.stephens, guettli, jribbens, mark.dickinson, pitrou, skip.montanaro, srittau, steve.roberts, tim_one, tomster ___ Python

[issue4256] optparse/argparse: provide a simple way to get a programmatically useful list of options

Éric Araujo added the comment: Hello Here’s another approach, which has to be used explicitly but provides much more flexible completion: http://pypi.python.org/pypi/optcomplete I ask the author some time ago if he’d adapt it to argparse; he answered he wouldn’t have time but it shouldn’t be

[issue2736] datetime needs an "epoch" method

Changes by Mark Dickinson : -- nosy: +amaury.forgeotdarc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue8487] os.mknod() fails on NFS mounted directories

Georg Brandl added the comment: Closing this, as it is not an issue with Python. -- nosy: +georg.brandl resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___

[issue1673409] datetime module missing some important methods

Alexander Belopolsky added the comment: On Wed, Apr 21, 2010 at 2:03 PM, Mark Dickinson wrote: .. > (BTW, as well as the newly introduced division methods, td.tosecs already > exists, except that it's spelt td.total_seconds.) Aggrrr! How did that slip in? :-) 8639913600.0 Shouldn't td.

[issue8478] tokenize.untokenize first token missing failure case

Changes by Georg Brandl : -- assignee: -> georg.brandl nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8483] asyncore.dispatcher's __getattr__ method produces confusing effects

Giampaolo Rodola' added the comment: You're absolutely right. Patch in attachment. -- keywords: +patch Added file: http://bugs.python.org/file17026/asyncore.patch ___ Python tracker

[issue8488] Docstrings of non-data descriptors "ignored"

New submission from Torsten Landschoff : [I would assign priority minor to this, but the tracker won't let me] I really like the online documentation features of python. However, I wonder about the output of the following simple example: class Descriptor(object): """Doc of a non-data descr

[issue5516] equality not symmetric for subclasses of datetime.date and datetime.datetime

Jess Austin added the comment: To be systematic, without the patch: >>> D(1900, 1, 1) > DT(1900, 1, 1) False >>> D(1900, 1, 1) < DT(1900, 1, 1) False >>> DT(1900, 1, 1) > D(1900, 1, 1) Traceback (most recent call last): File "", line 1, in TypeError: can't compare DT to D >>> DT(1900, 1, 1)

[issue8482] test_gdb - "(unable to read python frame information)" mismatch

Changes by Martin v. Löwis : -- assignee: -> dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Martin v. Löwis added the comment: That patch makes no sense. According to SSL_library_init(3SSL), "OpenSSL_add_ssl_algorithms() and SSLeay_add_ssl_algorithms() are synonyms for SSL_library_init()" So it shouldn't really matter which of these you call, and it should be sufficient to call onl

[issue8485] Don't accept bytearray as filenames, or simplify the API

Martin v. Löwis added the comment: I'm in favor of removing that support, too, but please check with python-dev whether anybody thinks a proper deprecation cycle (deprecated in 3.2, removed in 3.3) is needed. -- ___ Python tracker

[issue8314] test_ctypes fails in test_ulonglong on sparc buildbots

Mark Dickinson added the comment: I was going to say that I think that this issue can be closed now... ... but the src/sparc/v8.S file still looks wrong to me: Martin fixed one missing FFI_TYPE_UINT64 case, but it looks to me as though there's another one, in ffi_call_v8. The code starting

[issue8465] Backreferences vs. escapes: a silent failure solved

Changes by Georg Brandl : -- assignee: -> pitrou nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

Kees Cook added the comment: The stack protector will add 8 (aligned, so possibly padded) bytes to each stack frame of functions with arrays of 8 or greater bytes. So if things are marginal, this could make the difference between Pythons compiled with/without -fstack-protector. N.B. if rPat

[issue8465] re: Backreferences vs. escapes: a silent failure solved

Changes by STINNER Victor : -- title: Backreferences vs. escapes: a silent failure solved -> re: Backreferences vs. escapes: a silent failure solved ___ Python tracker ___ __

[issue5516] equality not symmetric for subclasses of datetime.date and datetime.datetime

Alexander Belopolsky added the comment: On Wed, Apr 21, 2010 at 2:33 PM, Jess Austin wrote: .. > It might seem like the latter behavior is marginally better, but really this > is just a mess, since a date-datetime comparison TypeErrors in all > directions.  I appreciate Alexander's more experi

[issue8484] ssl socket with certificate verification fails on SHA256 digest algorithm

Antoine Pitrou added the comment: > "OpenSSL_add_ssl_algorithms() and SSLeay_add_ssl_algorithms() are > synonyms for SSL_library_init()" The patch calls OpenSSL_add_all_algorithms(), though. (yes, it's a different one :-)) http://www.openssl.org/docs/crypto/OpenSSL_add_all_algorithms.html

  1   2   >