[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Mark Dickinson added the comment: The accumulated error doesn't need to exceed 1; it just needs to be enough to make (e.g.) leftover appear to be >= 0.5 when it's actually just less than 0.5. It shouldn't be too hard to find examples where this happens, but I haven't thought about it. > I

[issue8865] select.poll is not thread safe

Christian Schubert added the comment: okay, I've managed to put together a script that fairly consistently reproduces the problem on my (core2 duo 2,something GHz) machine some parameters (sleep times) are randomized in each iteration, the script runs for 30 iterations, each for 1 second, and

[issue8864] multiprocessing: undefined struct/union member: msg_control

Martin v. Löwis added the comment: Defining _XPG4_2 is surely the wrong thing to do, right? It's an internal flag only, not meant to be used by applications. -- ___ Python tracker _

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Alexander Belopolsky added the comment: I wonder if it would be justified to expose something like int _PyLong_IsOdd(PyObject *self) { PyLongObject *lo = (PyLongObject *)self; return Py_SIZE(lo) != 0 && ((lo->ob_digit[0] & 1) != 0); } in longobject.h? -- ___

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Alexander Belopolsky added the comment: Mark> (2) seems like overkill to me. I agree, however it would be interesting to figure out when accumulated errors can produce an inaccurate result. ISTM that leftover is the sum of up to 7 doubles each between 0 and 1 which is then rounded to the nea

[issue5023] Segfault in datetime.time.strftime("%z")

Alexander Belopolsky added the comment: Philipp, Why do you think you see the same problem as Eric? Can you set a trace on &tuple and see when it gets modified? Do you see the crash with zone_failure.py, test_datetime.py or both? -- ___ Python tra

[issue7583] Improve explanation of tab expansion in doctests

R. David Murray added the comment: In the absence of feedback about the doc patch, I have applied it in r81634. @techtonic: if I recall correctly I explained in your issue that had the patch what the problem was. Short summary: there are two equally valid ways in which tabs in the output and

[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute

R. David Murray added the comment: Committed in r81632. -- resolution: -> accepted stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue8864] multiprocessing: undefined struct/union member: msg_control

John Levon added the comment: This appears to be one of the few cases where there's incompatibilities between different versions of the standards. Old BSD sockets use msg_accrights*, whereas the more modern way is msg_control* pointing to a struct cmsghdr. In terms of user/kernel interface, t

[issue8867] serve.py (using wsgiref) cannot serve Python docs under Python3 due to encoding issues

New submission from R. David Murray : If you do a 'make serve' in the docs directory (after doing a make html, of course) and try to open the What's New link in the served doc pages, the following error results: ValueError: Unicode data must contain only code points representable in ISO-8859-

[issue8864] multiprocessing: undefined struct/union member: msg_control

Changes by Antoine Pitrou : -- nosy: +movement, zooko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue8866] socket.getaddrinfo() should support keyword arguments

Giampaolo Rodola' added the comment: ...also, the returning tuples could be named tuples instead. -- ___ Python tracker ___ ___ Python

[issue8866] socket.getaddrinfo() should support keyword arguments

New submission from Giampaolo Rodola' : As of now socket.getaddrinfo() only supports positional arguments, so that if I want to, say, specify "flags" argument I'm forced to specify "0" for other missing arguments: >>> socket.getaddrinfo("www.python.org", 0, 0, 0, socket.SOL_TCP) [(2, 1, 6, '',

[issue8865] select.poll is not thread safe

Antoine Pitrou added the comment: Do you have a script that reproduces it? -- assignee: d...@python -> components: -Documentation nosy: +pitrou versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 -Python 2.5 ___ Python tracker

[issue8865] select.poll is not thread safe

New submission from Christian Schubert : invoking select.poll.poll() concurrently from multiple threads frequently yields garbage in one thread: while poll_poll in thread 1 is parsing its result, another thread 2 calling poll may overwrite revents; assuming poll_result was 1 in thread 1 and th

[issue8864] multiprocessing: undefined struct/union member: msg_control

Sridhar Ratnakumar added the comment: Platforms affected: SunOS ginsu 5.10 Generic_125101-10 i86pc i386 i86pc SunOS nail 5.8 Generic_117350-55 sun4u sparc SUNW,Sun-Fire-280R Compiler used: bash-2.03$ which cc /opt/SUNWspro/bin//cc bash-2.03$ cc -V cc: Sun C 5.7 2005/01/07

[issue8864] multiprocessing: undefined struct/union member: msg_control

New submission from Sridhar Ratnakumar : There is apparently a regression on ^/trunk with multiprocessing on solaris10-x86 today. (used to work a few weeks before) cc -Kpic -OPT:Olimit=0 -g -DNDEBUG -O -IModules/_multiprocessing -I. -IInclude -I./Include -I/export/home/apy/rrun/build/activepyt

[issue5023] Segfault in datetime.time.strftime("%z")

Philipp Gortan added the comment: @belopolsky: unittest exists, /usr/lib/python2.6/test/test_datetime.py as mentioned by the OP, this unittest reproduces the issue. -- ___ Python tracker __

[issue1692335] Fix exception pickling: Move initial args assignment to BaseException.__new__

Tres Seaver added the comment: The attached patch adds Mark's examples to test_pickle as a failing test. -- nosy: +tseaver Added file: http://bugs.python.org/file17509/issue1692335-tests.patch ___ Python tracker

[issue8318] Deprecation of multifile inappropriate or incomplete

Tres Seaver added the comment: For the sake of completeness: the Zope2 trunk and its current stable branch now no longer use the multifile module, thanks to the following patch: http://svn.zope.org/Zope/trunk/src/OFS/tests/testRanges.py?rev=110704&r1=110402&r2=110704 That diff might serve a

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Mark Dickinson added the comment: Here's a first stab at a patch. It still needs tests. -- keywords: +patch Added file: http://bugs.python.org/file17508/issue8860.patch ___ Python tracker _

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Mark Dickinson added the comment: Aargh! No, I take that back. round() also does round-half-away-from-zero, of course. -- ___ Python tracker ___ __

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Mark Dickinson added the comment: This doesn't appear to be at all controversial; I don't think it's necessary to consult python-dev. (I haven't looked at the patch, though.) -- ___ Python tracker ___

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Mark Dickinson added the comment: I agree it would be nice to fix this. We could either (1) alter delta_new so that the final round uses round-to-nearest; this would give the desired behaviour in most cases, but there would still be a small possibility of rounding going in the wrong directi

[issue5023] Segfault in datetime.time.strftime("%z")

Changes by Alexander Belopolsky : -- stage: -> unit test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1100942] Add datetime.time.strptime and datetime.date.strptime

Alexander Belopolsky added the comment: Does this need to be brought up on python-dev for acceptance? -- nosy: +mark.dickinson stage: unit test needed -> patch review versions: +Python 3.2 -Python 2.7 ___ Python tracker

[issue3999] Real segmentation fault handler

STINNER Victor added the comment: > That's fine, but please provide a link to the new issue once you create it. Done: issue #8863. -- ___ Python tracker ___

[issue8863] Segfault handler: display Python backtrace on segfault

STINNER Victor added the comment: See also issue #3999: a similar patch to raise an exception on segfault. This patch was rejected because Python internal state may be corrupted, and we cannot guarantee that next instructions will be executed correctly. This patch is safer because it just tri

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

Alexander Belopolsky added the comment: Here is a shorter example of inconsistent behavior: >>> 0.5 * timedelta(microseconds=1) datetime.timedelta(0) >>> timedelta(microseconds=0.5) datetime.timedelta(0, 0, 1) -- ___ Python tracker

[issue8863] Segfault handler: display Python backtrace on segfault

New submission from STINNER Victor : Attached patch implements an handler for the signal SIGSEGV. It uses its own stack to be able to allocate memory on the stack (eg. call a function), even on stack overflow. The patch requires sigaction() and sigaltstack() functions, but I didn't patched co

[issue1289118] timedelta multiply and divide by floating point

Alexander Belopolsky added the comment: Committed in r81625. Fixed white space and added a note to "new in 3.2" section of the RST doc. -- resolution: -> accepted stage: commit review -> committed/rejected status: open -> closed ___ Python tracker

[issue8862] curses.wrapper does not restore terminal if curses.getkey() gets KeyboardInterrupt

New submission from July Tikhonov : Run test.py (below) in terminal, and interrupt it with Ctrl-C. Result: terminal settings are not restored (checked with linux console and xterm, with Python 2.7 and 3.2). # test.py # Broke it with KeyboardInterrupt import curses def main(screen): k = scr

[issue8861] curses.wrapper : unnessesary code

New submission from July Tikhonov : wrapper() code in Lib/curses/wrapper.py has an unnesesary line: res = None This variable is not used anywhere else in wrapper(). Inspecting the history of trunk, we can see that it was used used as a result of applying func(), but later was replaced by a

[issue6560] socket sendmsg(), recvmsg() methods

Antoine Pitrou added the comment: Would you like to upload your patch to http://codereview.appspot.com/? It would make reviewing easier. -- nosy: +pitrou ___ Python tracker ___

[issue6771] Curses.wrapper: documentation/implementation error

July Tikhonov added the comment: I think, since curses.wrapper is actually a function (and module named curses.wrapper cannot be trivially accessed), we can just modify docs, stripping out any mentions of module, instead documenting the function. We can leave the module 'curses.wrapper' and l

[issue8857] socket.getaddrinfo needs tests

Antoine Pitrou added the comment: Thanks for the comments. Other functions use "translate" too (gethostbyname, getservbyname, etc.), so I preferred to keep it for consistency. I've now committed the doc patch. -- ___ Python tracker

[issue8857] socket.getaddrinfo needs tests

Jean-Paul Calderone added the comment: About the doc patch: I like the word "Resolves" more than "Translate". "Resolves" implies possible network activity to me. "Translate" sounds like it's just a change in representation. Of course, things like `AI_NUMERICHOST` complicate things, since t

[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics

New submission from Alexander Belopolsky : >From issue1289118, msg106389: """ >>> from datetime import timedelta as d >>> [d(microseconds=i + .5)//d.resolution for i in range(-10,10)] [-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10] Should this be considered a bug? For

[issue7879] Too narrow platform check in test_datetime

Alexander Belopolsky added the comment: - 26backport committed in r81618. - merged to release31-maint in r81619. The skipIf patch blocked from release26-maint (skipIf is new in 2.7) and merged into release31-maint in r81620. -- stage: commit review -> committed/rejected status: open -

[issue8793] IDLE crashes on opening invalid file

Amaury Forgeot d'Arc added the comment: When running IDLE in a console, I get the error: Exception in Tkinter callback Traceback (most recent call last): File "c:\prod\python\lib\lib-tk\Tkinter.py", line 1410, in __call__ return self.func(*args) File "c:\prod\python\lib\idlelib\MultiCal

[issue1777412] Python's strftime dislikes years before 1900

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue1491] BaseHTTPServer incorrectly implements response code 100

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses

Antoine Pitrou added the comment: The problem was solved after running configure again. Sorry. -- resolution: -> invalid status: open -> closed ___ Python tracker ___ __

[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses

Antoine Pitrou added the comment: This is under Mandriva Linux 2010.1 (release candidate). Python 3.2a0 (py3k:81616, May 31 2010, 12:40:34) [GCC 4.4.3] on linux2 It seems ENABLE_IPV6 isn't defined: $ grep IPV6 pyconfig.h 32:/* #undef ENABLE_IPV6 */ Yet AF_INET6 is defined and has the same v

[issue1777412] Python's strftime dislikes years before 1900

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

[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses

Mark Dickinson added the comment: I'm not seeing this either, on SuSE Linux 10.3/amd64: Python 3.2a0 (py3k:81616, May 31 2010, 10:05:21) [GCC 4.2.1 (SUSE Linux)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import socket [55247 refs] >>> socket.getaddrinf

[issue8859] split() splits on non whitespace char when ther is no separator given.

Peter Landgren added the comment: So as a summary to what Ezio Melotti said: I should always specify encoding when calling split() to be sure nothing nasty happens? (Belive Ezio Melotti meant "calling split()" not "calling unicode()" in his last answer?) Thanks for pointing this out. ---