[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses
Martin v. Löwis mar...@v.loewis.de added the comment: What operating system is this on? What exact Python version are you using? I can't reproduce this with r81614 on Linux. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8858 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8859] split() splits on non whitespace char when ther is no separator given.
Peter Landgren peter.tal...@telia.com 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. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8859 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses
Mark Dickinson dicki...@gmail.com 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.getaddrinfo(www.python.org, 0)
[(2, 1, 6, '', ('82.94.164.162', 0)), (2, 2, 17, '', ('82.94.164.162', 0)), (2,
3, 0, '', ('82.94.164.162', 0)), (10, 1, 6, '', ('2001:888:2000:d::a2', 0, 0,
0)), (10, 2, 17, '', ('2001:888:2000:d::a2', 0, 0, 0)), (10, 3, 0, '',
('2001:888:2000:d::a2', 0, 0, 0))]
[58509 refs]
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8858
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses
Antoine Pitrou pit...@free.fr 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 value as returned by socket.getaddrinfo(): socket.AF_INET6 10 I'll try to ./configure again. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8858 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8858] socket.getaddrinfo returns wrong results for IPv6 addresses
Antoine Pitrou pit...@free.fr added the comment: The problem was solved after running configure again. Sorry. -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8858 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1491] BaseHTTPServer incorrectly implements response code 100
Changes by Éric Araujo mer...@netwok.org: -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1491 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1777412] Python's strftime dislikes years before 1900
Changes by Éric Araujo mer...@netwok.org: -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1777412 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8793] IDLE crashes on opening invalid file
Amaury Forgeot d'Arc amaur...@gmail.com 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\MultiCall.py, line 150, in handler r = l[i](event) File c:\prod\python\lib\idlelib\ScriptBinding.py, line 140, in run_module_event code = self.checksyntax(filename) File c:\prod\python\lib\idlelib\ScriptBinding.py, line 99, in checksyntax return compile(source, filename, exec) ValueError: invalid \x escape The crash in Bug#2 is certainly because pythonw.exe has no console, so sys.stdout blocks on the first flush(), after 4096 bytes of output. -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8793 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7879] Too narrow platform check in test_datetime
Alexander Belopolsky belopol...@users.sourceforge.net 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 - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7879 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
New submission from Alexander Belopolsky belopol...@users.sourceforge.net: 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 comparison, [d.resolution*(i+0.5)//d.resolution for i in range(-10,10)] [-10, -8, -8, -6, -6, -4, -4, -2, -2, 0, 0, 2, 2, 4, 4, 6, 6, 8, 8, 10] and [round(i+0.5) for i in range(-10,10)] [-10, -8, -8, -6, -6, -4, -4, -2, -2, 0, 0, 2, 2, 4, 4, 6, 6, 8, 8, 10] I checked the documentation and while it says: If any argument is a float and there are fractional microseconds, the fractional microseconds left over from all arguments are combined and their sum is rounded to the nearest microsecond. it does not specify how half-integers should be handled. While it may not be a bug in strict sense, it looks like the code in question can be improved. -- assignee: belopolsky messages: 106793 nosy: belopolsky, haypo, mark.dickinson, mcherm, rhettinger, stutzbach, tim_one priority: normal severity: normal stage: unit test needed status: open title: Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics type: feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8857] socket.getaddrinfo needs tests
Jean-Paul Calderone exar...@twistedmatrix.com 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 there may not actually be any network activity. The rest seems fine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8857 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8857] socket.getaddrinfo needs tests
Antoine Pitrou pit...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue8857 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6771] Curses.wrapper: documentation/implementation error
July Tikhonov july.t...@gmail.com 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 line 'from curses.wrapper import wrapper' in its current state, as implementation detail. Also, this is not backward incompatible in any case. Patch added. -- keywords: +patch nosy: +july Added file: http://bugs.python.org/file17505/curses-wrapper-doc.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6560] socket sendmsg(), recvmsg() methods
Antoine Pitrou pit...@free.fr added the comment: Would you like to upload your patch to http://codereview.appspot.com/? It would make reviewing easier. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6560 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8861] curses.wrapper : unnessesary code
New submission from July Tikhonov july.t...@gmail.com: 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 another construction. Patch added. -- components: Library (Lib) files: curses-wrapper-cleanup.patch keywords: patch messages: 106798 nosy: july priority: normal severity: normal status: open title: curses.wrapper : unnessesary code versions: Python 2.7, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file17506/curses-wrapper-cleanup.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8861 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8862] curses.wrapper does not restore terminal if curses.getkey() gets KeyboardInterrupt
New submission from July Tikhonov july.t...@gmail.com:
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 = screen.getkey()
curses.wrapper(main)
# Results are hardly readable due to the broken terminal.
# Something about KeyboardInterrupt
However, if getkey() is surrounded by try-except, behavior changes:
# test2.py
# Broke it with KeyboardInterrupt
import curses
def main2(screen):
try:
k = screen.getkey()
except KeyboardInterrupt:
raise
curses.wrapper(main2)
# Terminal is restored to its normal state.
In python3.2 test2.py results in traceback:
Traceback (most recent call last):
File test2.py, line 4, in main2
k = screen.getkey()
_curses.error: no input
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File test2.py, line 7, in module
curses.wrapper(main2)
File /usr/local/lib/python3.2/curses/wrapper.py, line 44, in wrapper
return func(stdscr, *args, **kwds)
File test2.py, line 4, in main2
k = screen.getkey()
KeyboardInterrupt
In 2.7 it results only in the latest part of traceback:
Traceback (most recent call last):
File test2.py, line 7, in module
curses.wrapper(main2)
File /usr/local/lib/python2.7/curses/wrapper.py, line 44, in wrapper
return func(stdscr, *args, **kwds)
File test2.py, line 4, in main2
k = screen.getkey()
KeyboardInterrupt
The problem is that instead of a single KeyboardInterrupt, two exceptions are
raised: KeyboardInterrupt and _curses.error('no input').
Possible solution is to suppress _curses.error in this case (since it is less
relevant than KeyboardInterrupt, IMO).
--
components: Library (Lib)
messages: 106799
nosy: july
priority: normal
severity: normal
status: open
title: curses.wrapper does not restore terminal if curses.getkey() gets
KeyboardInterrupt
type: behavior
versions: Python 2.7, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8862
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1289118] timedelta multiply and divide by floating point
Alexander Belopolsky belopol...@users.sourceforge.net 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 rep...@bugs.python.org http://bugs.python.org/issue1289118 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8863] Segfault handler: display Python backtrace on segfault
New submission from STINNER Victor victor.stin...@haypocalc.com: 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 configure.in script. These functions are available on Linux, but should be available on other UNIX OSes. segfault() signal handler supposes that the thread state is consistent (interp-frame chained list). It calls indirectly PyUnicode_EncodeUTF8() and so call PyBytes_FromStringAndSize() which allocates memory on the heap. It clears PyUnicode defenc attribute (the result of PyUnicode_EncodeUTF8()) to free directly the memory. To test it, try some scripts in Lib/test/crashers/. One example: $ ./python Lib/test/crashers/recursive_call.py Fatal Python error: segmentation fault Traceback (most recent call first): File Lib/test/crashers/recursive_call.py, line 12, depth 15715 File Lib/test/crashers/recursive_call.py, line 12, depth 15714 File Lib/test/crashers/recursive_call.py, line 12, depth 15713 ... File Lib/test/crashers/recursive_call.py, line 12, depth 3 File Lib/test/crashers/recursive_call.py, line 12, depth 2 File Lib/test/crashers/recursive_call.py, line 9, depth 1 Segmentation fault -- components: Interpreter Core files: segfault_handler.patch keywords: patch messages: 106801 nosy: haypo priority: normal severity: normal status: open title: Segfault handler: display Python backtrace on segfault versions: Python 3.2 Added file: http://bugs.python.org/file17507/segfault_handler.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
Alexander Belopolsky belopol...@users.sourceforge.net 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 rep...@bugs.python.org http://bugs.python.org/issue8860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8863] Segfault handler: display Python backtrace on segfault
STINNER Victor victor.stin...@haypocalc.com 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 tries to display the backtrace and then exit. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3999] Real segmentation fault handler
STINNER Victor victor.stin...@haypocalc.com added the comment: That's fine, but please provide a link to the new issue once you create it. Done: issue #8863. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3999 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1100942] Add datetime.time.strptime and datetime.date.strptime
Alexander Belopolsky belopol...@users.sourceforge.net 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 rep...@bugs.python.org http://bugs.python.org/issue1100942 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5023] Segfault in datetime.time.strftime(%z)
Changes by Alexander Belopolsky belopol...@users.sourceforge.net: -- stage: - unit test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5023 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
Mark Dickinson dicki...@gmail.com 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 direction as a result of accumulated errors in
'leftover_us'. Or (2) rewrite delta_new to do correct rounding in all cases,
by using integer arithmetic where necessary.
(2) seems like overkill to me.
For (1), it looks like it would be enough just to replace the round_to_long
function with:
static long
round_to_long(double x)
{
return (long)round(x);
}
Actually, at this point, one might as well just inline round_to_long.
Note that round_to_long is also called from datetime_from_timestamp.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8860
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1100942] Add datetime.time.strptime and datetime.date.strptime
Mark Dickinson dicki...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue1100942 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
Mark Dickinson dicki...@gmail.com added the comment: Aargh! No, I take that back. round() also does round-half-away-from-zero, of course. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
Mark Dickinson dicki...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue8860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8318] Deprecation of multifile inappropriate or incomplete
Tres Seaver tsea...@agendaless.com 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=110704r1=110402r2=110704 That diff might serve as fodder for updating the docs for the deprecation. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8318 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1692335] Fix exception pickling: Move initial args assignment to BaseException.__new__
Tres Seaver tsea...@agendaless.com 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 rep...@bugs.python.org http://bugs.python.org/issue1692335 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5023] Segfault in datetime.time.strftime(%z)
Philipp Gortan mephi...@gmx.net 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 rep...@bugs.python.org http://bugs.python.org/issue5023 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8864] multiprocessing: undefined struct/union member: msg_control
New submission from Sridhar Ratnakumar sridh...@activestate.com: 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 hon-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Include -I/export/home/apy/rrun/build/activepython-svn-trunk/buil d/pyhg_trunk-solaris10-x86-hgtip27-rrun/python -c /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c -o build/temp.solaris-2.10-i86pc-2.7/export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.o cc: Warning: illegal option -OPT:Olimit=0 /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 126: undefined struct/union member: msg_control /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 126: warning: improper pointer/integer combination: op = /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 127: undefined struct/union member: msg_controllen /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 130: warning: implicit function declaration: CMSG_FIRSTHDR /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 130: warning: improper pointer/integer combination: op = /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 134: improper member use: msg_controllen /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 135: warning: implicit function declaration: CMSG_DATA /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 161: undefined struct/union member: msg_control /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 161: warning: improper pointer/integer combination: op = /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 162: undefined struct/union member: msg_controllen /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 165: warning: improper pointer/integer combination: op = /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c, line 169: improper member use: msg_controllen cc: acomp failed for /export/home/apy/rrun/build/activepython-svn-trunk/build/pyhg_trunk-solaris10-x86-hgtip27-rrun/python/Modules/_multiprocessing/multiprocessing.c -- components: Build, Library (Lib) messages: 106813 nosy: srid priority: normal severity: normal status: open title: multiprocessing: undefined struct/union member: msg_control type: compile error versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8864] multiprocessing: undefined struct/union member: msg_control
Sridhar Ratnakumar sridh...@activestate.com 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 usage: cc [ options] files. Use 'cc -flags' for details This seems to have been introduced by fix for Issue1759169 -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8865] select.poll is not thread safe
New submission from Christian Schubert b...@apexo.de: 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 thread 2 managed to clear all revents before thread 1 started scanning ufds, thread 1 would iterate straight through all ufds, past its bounds (no bound checks there), and return the first out-of-bounds entry that happens to have revents != 0 this issue needs at least documentation (although bounds-checking to prevent garbage in the result wouldn't hurt) also, since there doesn't seem to be any locking w/ regards to ufds, it might be possible to corrupt python's heap, by concurrently invoking poll_register and poll_poll. poll_register could move the ufds array to another location while resizing it and poll_poll would subsequently overwrite memory that is not allocated anymore or allocated by someone else (did not test that) python 2.5.5 -- assignee: d...@python components: Documentation, Library (Lib) messages: 106815 nosy: apexo, d...@python priority: normal severity: normal status: open title: select.poll is not thread safe type: behavior versions: Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8865] select.poll is not thread safe
Antoine Pitrou pit...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue8865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8866] socket.getaddrinfo() should support keyword arguments
New submission from Giampaolo Rodola' g.rod...@gmail.com:
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, '', ('82.94.164.162', 0)), (10, 1, 6, '', ('2001:888:2000:d::a2', 0,
0, 0))]
socket.getaddrinfo(www.python.org, flags=socket.SOL_TCP)
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: getaddrinfo() takes no keyword arguments
--
components: Library (Lib)
messages: 106817
nosy: exarkun, giampaolo.rodola, pitrou
priority: normal
severity: normal
status: open
title: socket.getaddrinfo() should support keyword arguments
versions: Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8866
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8866] socket.getaddrinfo() should support keyword arguments
Giampaolo Rodola' g.rod...@gmail.com added the comment: ...also, the returning tuples could be named tuples instead. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8866 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8864] multiprocessing: undefined struct/union member: msg_control
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +movement, zooko ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8867] serve.py (using wsgiref) cannot serve Python docs under Python3 due to encoding issues
New submission from R. David Murray rdmur...@bitdance.com: 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-1 encoding -- components: Library (Lib) messages: 106819 nosy: r.david.murray priority: normal severity: normal status: open title: serve.py (using wsgiref) cannot serve Python docs under Python3 due to encoding issues type: behavior versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8867 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8864] multiprocessing: undefined struct/union member: msg_control
John Levon movem...@users.sourceforge.net 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, this difference is encoded as a MSG_XPG4_2 flag via a __xnet_recvmsg() re-define depending upon #ifdef _XPG4_2. The result being that it's impossible to use C99 and a modern struct msghdr together. This is less than ideal and I'm following it up internally. In terms of getting Python building again, it should be sufficient to define _XPG4_2 for the multiprocessing module compile only. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8845] Expose sqlite3 connection inTransaction as read-only in_transaction attribute
R. David Murray rdmur...@bitdance.com added the comment: Committed in r81632. -- resolution: - accepted stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8845 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7583] Improve explanation of tab expansion in doctests
R. David Murray rdmur...@bitdance.com 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 the spacing in the sample output could be reconciled; both have their problems. Therefore it is better to have the user handle it explicitly one way or another. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5023] Segfault in datetime.time.strftime(%z)
Alexander Belopolsky belopol...@users.sourceforge.net 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 tracker rep...@bugs.python.org http://bugs.python.org/issue5023 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
Alexander Belopolsky belopol...@users.sourceforge.net 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 nearest integer. I don't see how accumulated error can exceed 1 and affect the result. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8860 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8860] Rounding in timedelta constructor is inconsistent with that in timedelta arithmetics
Alexander Belopolsky belopol...@users.sourceforge.net 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?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8860
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8864] multiprocessing: undefined struct/union member: msg_control
Martin v. Löwis mar...@v.loewis.de 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 rep...@bugs.python.org http://bugs.python.org/issue8864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
