[issue8545] i didn't get rqrd output for programme in python?(plz... help)
Georg Brandl ge...@python.org added the comment: Please use python-h...@python.org or comp.lang.python for usage questions, not the tracker. -- nosy: +georg.brandl resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8545 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1462525] URI parsing library
Paul Jimenez p...@place.org added the comment: Since no one else has commented on this in over a year, and the new (2.6+) code works fine, I'll just close this to help clean things up. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1462525 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8128] String interpolation with unicode subclass fails to call __str__
Georg Brandl ge...@python.org added the comment:
In Python 2.x, __unicode__ is called instead of __str__. Whether that's
correct behavior, I'm not sure, but at least it is consistent with
{}.format(K()).
In Python 3.x, __unicode__ doesn't exist and __str__ isn't called; but for
{}.format(K()), it is. Therefore I think here a fix should be made in any
case.
Benjamin, what do you think?
--
assignee: - benjamin.peterson
nosy: +benjamin.peterson, georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8128
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4037] doctest.py should include method descriptors when looking inside a class __dict__
Georg Brandl ge...@python.org added the comment: So for staticmethods and classmethods, valname doesn't need to be reassigned? -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4037 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8546] The parameter buffering in _pyio.open doesn't work the same as in the builtin open
New submission from Patrick Sabin patricksa...@gmx.at: As far as I understand the _pyio.open function should resemble the builtin open, but in case of the buffering parameter, it doesn't. The builtin version doesn't allow None as argument, but this is the default in the _pyio.open signature. I attached a patch, which changes the default value of the buffering parameter to -1, which is the default in the builtin version. -- assignee: d...@python components: Documentation, Library (Lib) files: change_pyio_open_buffering_parameter.diff keywords: patch messages: 104301 nosy: d...@python, pyfex priority: normal severity: normal status: open title: The parameter buffering in _pyio.open doesn't work the same as in the builtin open type: behavior versions: Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file17103/change_pyio_open_buffering_parameter.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7384] curses crash on FreeBSD
Stefan Krah stefan-use...@bytereef.org added the comment: Roumen Petrov rep...@bugs.python.org wrote: Yes , I understand . For the protocol did gcc on FreeBSD warn if library order is -lncursesw -lreadline ? No. P.S. Issue with readline library linked to termcap compatible library on system that distribute more then one termcap compatible library is about 10 years old. I didn't want to touch the termcap logic. There's potential for breakage, and a real investigation would be time consuming. (There's a needless warning on Tiger about /usr/lib/termcap that could be fixed in another issue.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Charles-Francois Natali neolo...@free.fr added the comment:
@dabeaz
I'm getting random segfaults with your patch (even with the last one), pretty
much everywhere malloc or free is called.
Ater skimming through the code, I think the problem is due to gil_last_holder:
In drop_gil and take_gil, you dereference gil_last_holder-cpu_bound, but it
might very well happen that gil_last_holder points to a thread that has been
deleted (through tstate_delete_common). Dereferencing is not risky, because
there's a high chance that the address is still valid, but in drop_gil, you do
this:
/* Make the thread as CPU-bound or not depending on whether it was forced
off */
gil_last_holder-cpu_bound = gil_drop_request;
Here, if the thread has been deleted in meantine, you end up writting to a
random location on the heap, and probably corrupting malloc administration
data, which would explain why I get segfaults sometimes later on unrelated
malloc() or free() calls.
I looked at it really quickly though, so please forgive me if I missed
something obvious ;-)
@nirai
I have some more remarks on your patch:
- /* Diff timestamp capping results to protect against clock differences
* between cores. */
_LOCAL(long double) _bfs_diff_ts(long double ts1, long double ts0) {
I'm not sure I understand. You can have problem with multiple cores when
reading directly the TSC register, but that doesn't affect gettimeofday.
gettimeofday should be reliable and accurate (unless the OS is broken of
course), the only issue is that since it's wall clock time, if a process like
ntpd is running, then you'll run into problem
- pretty much all your variables are declared as volatile, but volatile was
never meant as a thread-synchronization primitive. Since your variables are
protected by mutexes, you already have all necessary memory barriers and
synchronization, so volatile just prevents optimization
- you use some funtions just to perform a comparison or substraction, maybe it
would be better to just remove those functions and perform the
substractions/comparisons inline (you declared the functions inline but there's
no garantee that the compiler will honor it).
- did you experiment with the time slice ? I tried some higher values and got
better results, without penalizing the latency. Maybe it could be interesting
to look at it in more detail (and on various platforms).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7946
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8128] String interpolation with unicode subclass fails to call __str__
Eric Smith e...@trueblade.com added the comment:
I agree with Georg. I think 2.x is arguably correct, and 3.1 is broken.
It looks like this has already been fixed in 3.2. It's not immediately obvious
why that is, I'll have to look at the code more than the quick glance I just
gave it.
Python 3.1.1+ (release31-maint:77299, Jan 4 2010, 08:27:32)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-13)] on linux2
Type help, copyright, credits or license for more information.
class MyStr(str):
... def __str__(self): return Surprise!
...
'%s' % MyStr('foo')
'foo'
'{}'.format(MyStr('foo'))
'Surprise!'
Python 3.2a0 (py3k:80525M, Apr 27 2010, 05:19:53)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-13)] on linux2
Type help, copyright, credits or license for more information.
class MyStr(str):
... def __str__(self): return Surprise!
...
'%s' % MyStr('foo')
'Surprise!'
'{}'.format(MyStr('foo'))
'Surprise!'
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8128
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Mark Dickinson dicki...@gmail.com added the comment: See issue 5516 for a related issue. -- nosy: +belopolsky, mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8540] Make Context._clamp public in decimal module
Stefan Krah stefan-use...@bytereef.org added the comment: (1) Perhaps I missed the relevant part in the spec, so I had to check what decNumber does: In the default context, clamp is 0, in the extended contexts, it is 1. So Python's ExtendedContext should indeed set _clamp to 1. (2) I agree about the importance of the formats, and I think they should be explicitly selectable like here: http://java.sun.com/j2se/1.5.0/docs/api/java/math/class-use/MathContext.html The current ExtendedContext is a bit of a vague concept, since it should be exactly one of DECIMAL32, DECIMAL64 or DECIMAL128. And none of these has prec=9. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8540] Make Context._clamp public in decimal module
Stefan Krah stefan-use...@bytereef.org added the comment: I knew it was somewhere: In the test case description, clamp=0 is specified as the default: http://speleotrove.com/decimal/dtfile.html#syntax -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8540] Make Context._clamp public in decimal module
Mark Dickinson dicki...@gmail.com added the comment:
Hmm. Yes, the spec itself is rather vague on the subject of clamping, so I
withdraw my claim that clamping is necessary for compliance with the spec. It
*is* necessary to make the those testcases with 'clamp=1' pass, though.
So from the point of view of compliance with the specification it's fine to
leave the _clamp attribute private.
I agree it would be useful to give easy access to the IEEE 754 formats, though,
for interoperability with C and Java (thanks for the Java link!). The most
important formats are decimal32, decimal64 and decimal128, but IEEE 754 also
specifies parameters for decimal{k} where k is any multiple of 32 bits.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8540
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Changes by David Beazley d...@dabeaz.com: Removed file: http://bugs.python.org/file17102/dabeaz_gil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
David Beazley d...@dabeaz.com added the comment: Added extra pointer check to avoid possible segfault. -- Added file: http://bugs.python.org/file17104/dabeaz_gil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8540] Make Context._clamp public in decimal module
Mark Dickinson dicki...@gmail.com added the comment: Re: ExtendedContext, the comments in decimal.py say: # Pre-made alternate contexts offered by the specification # Don't change these; the user should be able to select these # contexts and be able to reproduce results from other implementations # of the spec. This doesn't make a lot of sense to me, since (as Stefan says) the choice of precision 9 doesn't seem to come from the specification. However, the current ExtendedContext is used extensively in doctests and elsewhere; it would be awkward to change it now. I think adding the IEEE formats and encouraging users to use those in place of ExtendedContext might be the best bet. I'd also still want to make _clamp public in this case, to avoid people wondering why two apparently identical contexts (one with _clamp=1, one with _clamp=0) can lead to different results. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7384] curses crash on FreeBSD
Jeroen Ruigrok van der Werven asmo...@in-nomine.org added the comment: Stefan, I was emailing with Rong-En Fan, a FreeBSD committer, about this issue and he asked: Basically, this is caused by a) our readline.so is linked against ncurses.so (via -ltermcap which is the same lib) b) wide-character enabled ncurses, ncursesw.so, is also loaded in the same process To solve that, we need to have a separate termcap.so, do I understand the issue correctly? He also mentioned that [a]nother more aggressive way is to make only ncursesw installed into the system which requires a recompilation of all ports that use ncurses (ncurses and ncursesw are source compatible, but in most cases they are binary compatible as long as application don't assume size of ncurses structures). Which I fully support, it's something that I did on DragonFly BSD a long time ago already (for all I can remember). Your opinion? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Charles-Francois Natali neolo...@free.fr added the comment:
I don't see segfaults anymore, but there's still an unsafe dereference of
gil_last_holder inside take_gil:
/* Wait on the appropriate GIL depending on thread's classification */
if (!tstate-cpu_bound) {
/* We are I/O bound. If the current thread is CPU-bound, force it off
now! */
if (gil_last_holder-cpu_bound) {
SET_GIL_DROP_REQUEST();
}
You're still accessing a location that may have been free()'d previously: while
it will work most of the time (that's why I said it's not as risky), if the
page gets unmapped between the time the current thread is deleted and the next
thread takes over, you'll get a segfault. And that's undefined behaviour anyway
;-)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7946
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8547] unittest test discovery can fail when package under test is also installed globally
New submission from Michael Foord mich...@voidspace.org.uk: When test discovery is invoked on a package on the filesystem which is also installed in site-packages then importing the tests will look in the installed version. This causes discovery to run the wrong tests or fail. We can detect this (compare the __file__ against the expected location) and also insert the top level path as the first location in sys.path instead of appending it to the end. If we detect a failed import then we should error out with an appropriate message. (Nose gets round this by patching __import__ to import from a specific location which seems potentially fragile.) -- assignee: michael.foord components: Library (Lib) messages: 104313 nosy: michael.foord priority: normal severity: normal stage: needs patch status: open title: unittest test discovery can fail when package under test is also installed globally type: behavior versions: Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
donal djeo donaldje...@gmail.com added the comment:
I'm getting random segfaults with your patch (even with the last one), pretty
much everywhere malloc or free is called.
Ater skimming through the code, I think the problem is due to gil_last_holder:
In drop_gil and take_gil, you dereference gil_last_holder-cpu_bound, but it
might very well happen that gil_last_holder points to a thread that has been
deleted (through tstate_delete_common). Dereferencing is not risky, because
there's a high chance that the address is still valid, but in drop_gil, you do
this:
/* Make the thread as CPU-bound or not depending on whether it was forced off */
gil_last_holder-cpu_bound = gil_drop_request;
Here, if the thread has been deleted in meantine, you end up writting to a
random location on the heap, and probably corrupting malloc administration
data, which would explain why I get segfaults sometimes later on unrelated
malloc() or free() calls.
I looked at it really quickly though, so please forgive me if I missed
something obvious ;-)
@nirai
I have some more remarks on your patch:
- /* Diff timestamp capping results to protect against clock differences
* between cores. */
_LOCAL(long double) _bfs_diff_ts(long double ts1, long double ts0) {
I'm not sure I understand. You can have problem with multiple cores when
reading directly the TSC register, but that doesn't affect gettimeofday.
gettimeofday should be reliable and accurate (unless the OS is broken of
course), the a href=http://www.mcpexams.net;mcp/a only issue is that since
it's wall clock time, if a process like ntpd is running, then you'll run into
problem
- pretty much all your variables are declared as volatile, but volatile was
never meant as a thread-synchronization primitive. Since your variables are
protected by mutexes, you already have all necessary memory barriers and
synchronization, so volatile just prevents optimization
- you use some funtions just to perform a comparison or substraction, maybe it
would be better to just remove those functions and perform the
substractions/comparisons inline (you declared the functions inline but there's
no garantee that the compiler will honor it).
- did you experiment with the time slice ? I tried some higher values and got
better results, without penalizing the latency. Maybe it could be interesting
to look at it in more detail (and on various platforms).
--
components: +None -Interpreter Core
nosy: +donaldjeo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7946
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Changes by Antoine Pitrou pit...@free.fr: -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Changes by Antoine Pitrou pit...@free.fr: -- components: +Interpreter Core -None ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7833] Bdist_wininst installers fail to load extensions built with Issue4120 patch
Koen van de Sande k...@tibed.net added the comment: There should be no manifest embedded into wininst, because then the cases which Issue 4120 fixed (a CRT installed into a local folder, instead of system-wide, due to limited access rights), will 'break' again: the installer can then no longer work unless there is a system-wide installation of the CRT. Option #1, #2 and #3 all sound reasonable (and #2 is the current situation). I have some doubts about option #4: it is a very specific use case, and then the whole benefit of issue 4120 is lost, because stripping runtimes would have to be removed again. Why is putting a separate manifest file next to the DLL not an option? Combined with #3 (allow extension developer to disable embedding of manifests) a separate manifest can fix the problem. -- nosy: +koen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7833 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7384] curses crash on FreeBSD
Stefan Krah stefan-use...@bytereef.org added the comment: Jeroen Ruigrok van der Werven rep...@bugs.python.org wrote: Stefan, I was emailing with Rong-En Fan, a FreeBSD committer, about this issue and he asked: Basically, this is caused by a) our readline.so is linked against ncurses.so (via -ltermcap which is the same lib) b) wide-character enabled ncurses, ncursesw.so, is also loaded in the same process To solve that, we need to have a separate termcap.so, do I understand the issue correctly? Yes, only that the separate termcap is called libtinfo.so. The approach of splitting out libtinfo from ncurses (used by Fedora) is the most flexible and allows the user to choose ncurses or ncursesw. [ste...@fedora-amd64 ~]$ ldd /lib64/libreadline.so.6.0 linux-vdso.so.1 = (0x7fff725ff000) libtinfo.so.5 = /lib64/libtinfo.so.5 (0x0036e4a0) libc.so.6 = /lib64/libc.so.6 (0x0036d960) /lib64/ld-linux-x86-64.so.2 (0x0036d920) +ports that use ncurses (ncurses and ncursesw are source compatible, but in most cases they are binary compatible as long as application don't +assume size of ncurses structures). Which I fully support, it's something that I did on DragonFly BSD a long time ago already (for all I can remember). Your opinion? I think the libtinfo approach is more flexible, and I'm not aware of any drawbacks. So, for FreeBSD, I'd use it. Stefan Krah -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Changes by Guilherme Salgado gsalg...@gmail.com: -- nosy: -salgado ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
David Beazley d...@dabeaz.com added the comment: That second access of gil_last_holder-cpu_bound is safe because that block of code is never entered unless some other thread currently holds the GIL. If a thread holds the GIL, then gil_last_holder is guaranteed to have a valid value. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7833] Bdist_wininst installers fail to load extensions built with Issue4120 patch
Koen van de Sande k...@tibed.net added the comment: Concerning the patch: what happens when the developer already added /MANIFEST:NO to the flags, and the code deduces that MSVCR9 is the only runtime, e.g. the case where /MANIFEST:NO is in the flags twice? Does the linker handle this OK, or does there need to be an additional check as to not have it twice? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7833 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Charles-Francois Natali neolo...@free.fr added the comment:
Didn't have much sleep last night, so please forgive me if I say something
stupid, but:
Python/pystate.c:
void
PyThreadState_DeleteCurrent()
{
PyThreadState *tstate = _PyThreadState_Current;
if (tstate == NULL)
Py_FatalError(
PyThreadState_DeleteCurrent: no current tstate);
_PyThreadState_Current = NULL;
tstate_delete_common(tstate);
if (autoTLSkey PyThread_get_key_value(autoTLSkey) == tstate)
PyThread_delete_key_value(autoTLSkey);
PyEval_ReleaseLock();
}
the current tstate is deleted and freed before releasing the GIL, so if another
thread calls take_gil after the current thread has called tstate_delete_common
but before it calls PyEval_ReleaseLock (which calls drop_gil and set gil_locked
to 0), then it will enter this section and dereference gil_last_holder.
I just checked with valgrind, and he also reports an illegal dereference at
this precise line.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7946
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
David Beazley d...@dabeaz.com added the comment: I stand corrected. However, I'm going to have to think of a completely different approach for carrying out that functionality as I don't know how the take_gil() function is able to determine whether gil_last_holder has been deleted or not. Will think about it and post an updated patch later. Do you have any examples or insight you can provide about how these segfaults have shown up in Python code? I'm not able to observe any such behavior on OS-X or Linux. Is this happening while running the ccbench program? Some other program? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7027] test_io.py: codecs.IncrementalDecoder is sometimes None
STINNER Victor victor.stin...@haypocalc.com added the comment: Same error here: http://www.python.org/dev/buildbot/builders/AMD64 Ubuntu 2.6/builds/555/steps/test/logs/stdio (codecs_none.txt is a copy of stdio) -- nosy: +haypo Added file: http://bugs.python.org/file17105/codecs_none.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2810] _winreg.EnumValue sometimes raises WindowsError (More data is available)
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- title: _winreg.EnumValue fails when the registry data includes multibyte unicode characters - _winreg.EnumValue sometimes raises WindowsError (More data is available) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2810 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8540] Make Context._clamp public in decimal module
Stefan Krah stefan-use...@bytereef.org added the comment:
I'd prefer to drop the ExtendedContext completely. Reasons are:
1) _clamp, prec, emin and emax aren't set to IEEE754 values.
2) The use of 'extended' is decNumber specific (see
http://speleotrove.com/decimal/dncont.html ). In IEEE754
'extended' has yet another meaning (AFAICS).
I can see that it is awkward to remove it, but if there's consensus
I'd be willing to work on a patch.
Making clamp visible sounds fine to me. (Personally, I'd rather have
capitals non-visible.)
If we make Decimal{32,64,128} contexts available, we should document exactly
how the arithmetic deviates from IEEE754.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8540
___
___
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
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- nosy: +stutzbach ___ 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
[issue8128] String interpolation with unicode subclass fails to call __str__
Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com added the comment: It's probably a duplicate of issue #1583863. -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Changes by David Beazley d...@dabeaz.com: Removed file: http://bugs.python.org/file17104/dabeaz_gil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Charles-Francois Natali neolo...@free.fr added the comment: Do you have any examples or insight you can provide about how these segfaults have shown up in Python code? I'm not able to observe any such behavior on OS-X or Linux. Is this happening while running the ccbench program? Some other program? If you're talking about the first issue (segfaults due to writting to gil_last_holder-cpu_bound), it was occuring quite often during ccbench (pretty much anywhere malloc/free was called). I'm running a regular dual-core Linux box, nothing special. For the second one, I didn't observe any segfault, I just figured this out reading the code and confirmed it with valgrind, but it's much less likely because the race window is very short and it also requires that the page is unmmaped in between. If someone really wanted to get segfaults, I guess a good start would be: - get a fast machine, multi-core is a bonus - use a kernel with full preemption - use a lot of threads (-n option with ccbench) - use purify or valgrind --free-fill option so that you're sure to jump to noland if you dereference a previously-free'd pointer -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
David Beazley d...@dabeaz.com added the comment: One more attempt at fixing tricky segfaults. Glad someone had some eagle eyes on this :-). -- Added file: http://bugs.python.org/file17106/dabeaz_gil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8128] String interpolation with unicode subclass fails to call __str__
Eric Smith e...@trueblade.com added the comment: Yes, that's the cause, thanks for finding that issue. It's actually fixed in 3.1.2, I just hadn't updated my local copy. Closing, since there's nothing to fix here. The 2.6 behavior is correct, and the 3.x behavior that was broken has been fixed. -- resolution: - duplicate status: open - closed superseder: - __str__ cannot be overridden on unicode-derived classes ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: Is there a patch with a fix or just a patch with a test. If the later, maybe someone can remove a patch keyword. -- nosy: +Alexander.Belopolsky -belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Thomas W. Barr t...@rice.edu added the comment: It's just a test. Finishing the patch completely slipped my mind. I'll work on it later tonight. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment: You're right. I asked Thomas the wrong question, and the Keywords and Stage need updating. Thomas, do you still plan to submit a patch that fixes the problem? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Nir Aides n...@winpdb.org added the comment:
On Tue, Apr 27, 2010 at 12:23 PM, Charles-Francois Natali wrote:
@nirai
I have some more remarks on your patch:
- /* Diff timestamp capping results to protect against clock differences
* between cores. */
_LOCAL(long double) _bfs_diff_ts(long double ts1, long double ts0) {
I'm not sure I understand. You can have problem with multiple cores when
reading directly the
TSC register, but that doesn't affect gettimeofday. gettimeofday should be
reliable and accurate
(unless the OS is broken of course), the only issue is that since it's wall
clock time, if a process
like ntpd is running, then you'll run into problem
I think gettimeofday() might return different results on different cores as
result of kernel/hardware problems or clock drift issues in VM environments:
http://kbase.redhat.com/faq/docs/DOC-7864
https://bugzilla.redhat.com/show_bug.cgi?id=461640
In Windows the high-precision counter might return different results on
different cores in some hardware configurations (older multi-core processors).
I attempted to alleviate these problems by using capping and by using a python
time counter constructed from accumulated slices, with the assumption that IO
bound threads are unlikely to get migrated often between cores while running. I
will add references to the patch docs.
- did you experiment with the time slice ? I tried some higher values and got
better results,
without penalizing the latency. Maybe it could be interesting to look at it
in more detail (and
on various platforms).
Can you post more details on your findings? It is possible that by using a
bigger slice, you helped the OS classify CPU bound threads as such and improved
synchronization between BFS and the OS scheduler.
Notes on optimization of code taken, thanks.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7946
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Thomas W. Barr t...@rice.edu added the comment: I'm still reasonably new to the codebase, but I'm certainly going to try to fix the issue. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment: Great! If you get stuck or have a question, just ask. :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- keywords: -patch stage: unit test needed - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2810] _winreg.EnumValue sometimes raises WindowsError (More data is available)
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- assignee: - stutzbach keywords: +needs review stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2810 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6672] Add Mingw recognition to pyport.h to allow building extensions
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- components: +Windows stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6672 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5553] Py_LOCAL_INLINE(type) doesn't actually inline except using MSC
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- assignee: - stutzbach priority: - low stage: - needs patch type: - performance versions: +Python 3.2 -Python 2.7, Python 3.0, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5553 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4295] closing stdout in a child process on cygwin means that process doesn't receive bytes from stdin anymore. I think.
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- resolution: - works for me stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4295 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue808164] socket.close() doesn't play well with __del__
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- assignee: - stutzbach versions: +Python 2.7, Python 3.2 -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue808164 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7079] file_close() ignores return value of close_the_file
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- keywords: +needs review stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7079 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7079] file_close() ignores return value of close_the_file
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- assignee: gregory.p.smith - stutzbach stage: patch review - unit test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7079 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Changes by Daniel Stutzbach dan...@stutzbachenterprises.com: -- assignee: - stutzbach ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Alexander Belopolsky alexander.belopol...@gmail.com added the comment: Before someone spends more time writing a patch, lets pause and consider whether this is a bug in the first place. My understanding of the issue is that given class A(object): ... def __eq__(self, other): ...return True ... OP expects date(1,1,1) == A() to return True, but instead date(1,1,1) == A() False Note that this problem can be worked around by endowing A with a timetuple attribute: A.timetuple=1 Now date(1,1,1) == A() True This is a documented feature: In order to stop comparison from falling back to the default scheme of comparing object addresses, date comparison normally raises TypeError if the other comparand isn’t also a date object. However, NotImplemented is returned instead if the other comparand has a timetuple() attribute. This hook gives other kinds of date objects a chance at implementing mixed-type comparison. If not, when a date object is compared to an object of a different type, TypeError is raised unless the comparison is == or !=. The latter cases return False or True, respectively. http://docs.python.org/release/2.6.5/library/datetime.html#datetime.date.day (Note 4) I am adding Tim to the nosy list because he appears to be the author of the relevant code. It is my understanding that this issue can only be regarded as an RFE. Given the fact that 2.x is approaching bug fix only stage (if it is not already there) and the problem is fixed in 3.x, I recommend closing this as won't fix. Mark, No, I don't think this is directly related to issue 5516. -- nosy: +tim_one ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8548] Building on CygWin 1.7: PATH_MAX redefined
New submission from Jeff Binder extru...@gmail.com: Building Python 3.1.2 on Cygwin 1.7, I got errors in main.c stemming from a warning: PATH_MAX redefined (see attached log). I got around this by commenting out the #define. I don't know if the best solution is #ifndef, #undef, or something else. . . . I know CygWin has changed the value of PATH_MAX in 1.7 (see: http://www.cygwin.com/cygwin-ug-net/ov-new1.7.html), though I'm not sure why that would cause this problem. -- components: Installation files: python-build-logs.tar.gz messages: 104334 nosy: jbinder priority: normal severity: normal status: open title: Building on CygWin 1.7: PATH_MAX redefined type: compile error versions: Python 3.1 Added file: http://bugs.python.org/file17107/python-build-logs.tar.gz ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8506] SimpleXMLRPCServer Socket not closed after shutdown call
Changes by Santoso Wijaya santa@me.com: -- nosy: +santa4nt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8506 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7946] Convoy effect with I/O bound threads and New GIL
Antoine Pitrou pit...@free.fr added the comment: I stand corrected. However, I'm going to have to think of a completely different approach for carrying out that functionality as I don't know how the take_gil() function is able to determine whether gil_last_holder has been deleted or not. Please note take_gil() currently doesn't depend on the validity of the pointer. gil_last_holder is just used as an opaque value, equivalent to a thread id. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8060] PEP 3101 string formatting missing engineering presentation type for floating point
Terry J. Reedy tjre...@udel.edu added the comment: Too late for 2.7, but I would like this to hit 3.2. Some calculators have engineering format as an output option and it would be good for Python. This issue is being discussed in python-list in thread Engineering numerical format The OP (or someone) posted an Engineer(float) class with a .format method that does what *he* would like. Participants have been invited by Mark to comment here. It was noted that Decimal has a .to-engineering-string method, but it follows the standard at page 20 of speleotrove.com/decimal/decarith.pdf which is different from what is being asked for. -- nosy: +tjreedy versions: -Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8060 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7027] test_io.py: codecs.IncrementalDecoder is sometimes None
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +amaury.forgeotdarc, loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7027] test_io.py: codecs.IncrementalDecoder is sometimes None
STINNER Victor victor.stin...@haypocalc.com added the comment: module-dealloc() was changed by #7140 by r75437: imp.new_module does not function correctly if the module is returned from a function and used directly. Can we backport the fix to 2.6? It would be complex to write a workaround in the tests. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7027] test_io.py: codecs.IncrementalDecoder is sometimes None
STINNER Victor victor.stin...@haypocalc.com added the comment: Here is a workaround. I didn't expected a short patch, but it's enough. -- keywords: +patch Added file: http://bugs.python.org/file17108/regrtest_preload_ascii.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5727] doctest pdb readline broken
Sriram sriramrathinav...@yahoo.com added the comment: Hi, I believe this behaviour can be tested if we can prove that Cmd's cmdloop uses raw_input to get the data as against self.stdin.readline(). To test it, ideally I would have liked to override sys.stdin with a fake input stream and pass the list of args (like it's done in test_doctest.py). I can then pass the character codes for Up and Down Arrows in our fake stream and check if the raw_input can use readline and move through the fake input stream but that won't be possible because the C implementation of raw_input uses the readline functionality if only both stdin and stdout are from a terminal. So alternatively, if we can just ensure that doctest's pdb (_OutputREdirectingPdb) has use_rawinput as 1, we can be assured that readline will be used. I have attached the svn diff with trunk. Please review and comment Thanks Sriram -- Added file: http://bugs.python.org/file17109/pdbreadline.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5727 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7833] Bdist_wininst installers fail to load extensions built with Issue4120 patch
Christoph Gohlke cgoh...@uci.edu added the comment: I have some doubts about option #4: it is a very specific use case, and then the whole benefit of issue 4120 is lost Pythoncom are pywintypes are indeed special cases: Out of the 170 DLL files in my Python site-packages directory, these seem to be the only ones built with distutils. All other DLLs are apparently built without Python involvement using make, nmake, CMake, or Visual Studio and most of them contain embedded manifests, which is the default when using nmake, CMake, or Visual Studio. Practically, to make a standalone distribution of any Python 2.6/3.1 application with external DLL dependencies likely requires to provide external manifest files. The issue4120 patch does not change this situation and I don't see any sane way to patch Python/distutils that could. The main benefit of the issue4120 patch, as I see it, is that PYD files produced by distutils work in a standalone distribution without any further attention. Msvc9compiler_stripruntimes_revised.patch does not change this. My reasoning for this patch (besides fixing the bdist_wininst installer issue) was to allow the popular pywin32 package to build without changes, and offer a way for other extension packages to exclude manifests from DLL files if required (apparently not that common). Alternatively one could provide a mechanism to embed specific manifests into DLLs. Is that currently possible? Then pywin32 setup.py could be fixed. Why is putting a separate manifest file next to the DLL not an option? Because the pythoncom dll is currently installed into the Windows system directory. Putting manifest files there will pollute the system directory even more and possibly interfere with other system components if not done right (not tested). But again, pywin32 setup.py could be fixed to not install the DLL/manifest files into the system directory. Which Python packages other than pywin32 build DLL files via distutils? I don't know any. Can anyone provide a minimal setup.py script and C file that produces a DLL file for testing? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7833 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8060] PEP 3101 string formatting missing engineering presentation type for floating point
Mark Dickinson dicki...@gmail.com added the comment: After the all-important issue of what letter to use (the folks on the python-list thread suggested 'm', and it seems as good a letter as any, so I'll use it in the examples below), there are some open questions: (1) The exact form of the output needs to be determined. For a nonzero finite number, I'm guessing the output should look something like: 'signdigits.digitseexponent with at least 1 and at most 3 digits to the left of the point (and the first of those digits being nonzero). Is this about right? The sign would be controlled in the same way as for 'e', 'f' and 'g' formatting. Would the exponent be included even when it's zero, or should it be omitted in that case? (We'd need to determine how to output zeros, nans and infinities, too, but that shouldn't be a big issue.) (2) When doing something like 'format(x, '.5m')', what would the 5 refer to? The two options I see are (a) number of significant digits, or (b) number of digits to the right of the point. The former seems to make more sense mathematically, but might be a bit awkward when it comes to aligning results in a table: format(3.2, '.5m') - 3.2e+00 format(13.2, '.5m') - 13.2000e+00 The latter results in different numbers of significant digits depending on where the exponent lies. Hmm. Perhaps there's also (c): number of places to the right of the *true* decimal point, so that 'm' is more analogous to 'f' than to 'e'. (3) What should the default precision be? 6 is what's used for 'e', 'f' and 'g' formatting, so should probably also be used for 'm'. (4) When (if ever) should trailing zeros and a trailing decimal point be omitted (like 'g' formatting does). I'd say never. (5) What should the decimal module do? Call to_eng_string, or try to match float's behaviour? Formatting for the decimal type has the added complication of trying to preserve significant zeros where possible; this might require some thought. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8060 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8543] asynchat documentation issues
Josiah Carlson josiahcarl...@users.sourceforge.net added the comment: The suggested documentation changes sound good to me. Those items that aren't documented may need a note that they are deprecated and will be removed in the future, but I'd consider that optional. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8543 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8540] Make Context._clamp public in decimal module
Mark Dickinson dicki...@gmail.com added the comment:
I'd prefer to drop the ExtendedContext completely.
We have to be careful not to break existing 3rd party code, though. A
newly-designed decimal module, prepared with 20/20 hindsight, probably wouldn't
include an ExtendedContext with the current definition. But we're not dealing
with a newly-designed module: we're dealing with a well-established and
well-used module, so there's not a lot of scope for removals or major behaviour
changes.
Personally, I don't think the design error (if there is a design error here) is
big enough to make it worth breaking backwards compatibility. I'd rather leave
ExtendedContext in for the duration of Python 3.x, but introduce better options
and steer (via the documentation) new decimal users towards those.
(BTW, Python takes backwards compatibility pretty seriously: see PEP 387 for a
write-up of the policy.)
If we make Decimal{32,64,128} contexts available, we should document exactly
how the arithmetic deviates from IEEE754.
Possibly, though that's less important to me than just being able to read and
write values in these formats produced by other systems.
Were you thinking of any deviations in particular?
Making clamp public should be straightforward enough though, and is independent
of the changes discussed above; I'll see if I can come up with a patch. (Even
here, though, I think it makes sense to leave the private _clamp attribute in
place in case people are using it; a new public 'clamp' property can be added
that wraps the _clamp attribute.)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8540
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8005] datetime's comparison methods do not return NotImplemented when they should
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment: Thanks for pointing that out. For what it's worth, if I understand the documentation correctly the goal is to prevent the following misleading comparisons: date with time datetime with date datetime with time datetime w/ timezone with datetime w/o timezone time w/ timezone with time w/o timezone It's unfortunate that it throws a TypeError for all comparisons (unlike complex numbers which only throw a TypeError when comparing with numbers), but I suppose you are right that it's too late to fix this in 2.x. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8005 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7027] test_io.py: codecs.IncrementalDecoder is sometimes None
STINNER Victor victor.stin...@haypocalc.com added the comment: Can we backport the fix to 2.6? It's too late to fix such subtle bug in module machinery, so I commited my workaround in regrtest.py: r80538. Wait for the buildbots before closing the issue. test_io and/or test_codecs failed on buildbots: - AMD64 Ubuntu 2.6 (r80535) - x86 Tiger 2.6 (r80535) - x86 Windows7 2.6 (r80531) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8549] Modules/_ssl.c: extra comma breaks build on AIX
New submission from Sridhar Ratnakumar sridh...@activestate.com:
Modules/_ssl.c
gu...@36917
64
enum py_ssl_version {
gu...@36917
65
PY_SSL_VERSION_SSL2,
gu...@36917
66
PY_SSL_VERSION_SSL3,
gu...@36917
67
PY_SSL_VERSION_SSL23,
gu...@36917
68
PY_SSL_VERSION_TLS1,
gu...@36917
69
};
Attached patch fixes this issue.
--
components: Build
messages: 104347
nosy: srid
priority: normal
severity: normal
status: open
title: Modules/_ssl.c: extra comma breaks build on AIX
versions: Python 2.6, Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8549
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8549] Modules/_ssl.c: extra comma breaks build on AIX
Changes by Sridhar Ratnakumar sridh...@activestate.com: -- keywords: +patch Added file: http://bugs.python.org/file17110/fix-extra-comma-aix.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8549] Modules/_ssl.c: extra comma breaks build on AIX
Antoine Pitrou pit...@free.fr added the comment: Thank you very much! Committed in r80540 (trunk), r80541 (2.6), r80542 (py3k), r80543 (3.1). -- nosy: +pitrou resolution: - fixed stage: - committed/rejected status: open - pending versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8549] Modules/_ssl.c: extra comma breaks build on AIX
Changes by Antoine Pitrou pit...@free.fr: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8493] socket's send can raise errno 35 under OS X, which causes problems in sendall
Matthew Cowles mdcow...@users.sourceforge.net added the comment: Apologies! Further investigation indicates that the user had set a timeout in the ftplib module. I'll close this. In an ideal world, errors due to timeouts would look like they were related to timeouts. But that's a different matter entirely. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8493 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8060] PEP 3101 string formatting missing engineering presentation type for floating point
Keith Brafford keith.braff...@gmail.com added the comment: Ok, let's zero in on how this should work. I'll start the concrete proposal discussion in terms of how it would have worked with the old-style specifiers (since I am more familiar with that method) and we can bring it up to Py3K standards as a group. I was thinking something along these lines: %[space | 0 ][.precision]m where the optional space or zero means that you want the whole number part of the output to be padded to three digits, either with spaces or prepended zeroes. No space or zero means no prepending of anything. The .precision would be the number of digits after the decimal point you want to see. If you don't specify this, then the default would be something that people agreed made the most sense, say 4 for now. f = math.pi * 1e-5 print f 3.1415926535897935e-005 print %m % f 31.4159e-06 print % m % f 31.4159e-06 print %0m % f 031.4159e-06 print % m.6 % f 31.415927e-06 Mark brought up this point: e.g. format(12345.678, '.5m'): Should the '5' indicate 5 digits after the point (giving '12.34568e+3' in this case), or 5 significant digits in total (giving '12.345e+3'). I tend to think that it's more important that the precision number tell you the number of digits after the decimal point. This is because the underlying float still has all of the precision, and the format specifier is used simply to make the printout look correct. Being able to specify that you want three slots before the point, then a constant number after the point lets you get perfectly aligned columns in a tabular printout without a lot of fuss. I wrote a class that I've been using to test these formats out with (attached). I use it like this: from efloat impot EFloat as E it has a class precision value that you can set: E.precision = 5 E(math.pi) 3.14159e+0 E(math.pi / 1e-9) 3.14159e+9 E(math.pi / 1e-2) 314.15927e+0 E(math.pi / 1e-5) 314.15927e+3 It has a slight bug, though. It doesn't give me two digits of exponent, which would be required in the engineering format specifier, IMHO, so that programmers can easily get constant tabular column widths. -- nosy: +Keith.Brafford Added file: http://bugs.python.org/file17111/efloat.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8060 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7865] io close() swallowing exceptions
Antoine Pitrou pit...@free.fr added the comment: I just tried the patch. One problem is that you are supposed to be able to call close() several times without having it fail: f = open(LICENSE) f.close() f.close() f = io.open(LICENSE) f.close() f.close() Traceback (most recent call last): File stdin, line 1, in module ValueError: I/O operation on closed file. This means your patch should be a little smarter. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7865 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: astraw: I've been playing with stdeb. I think it's a nice implementation of bdist_deb, but it doesn't seem to include the dh_make/debianize functionality of this patch. Is that the case or have I missed something? -- nosy: +barry ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7079] file_close() ignores return value of close_the_file
Antoine Pitrou pit...@free.fr added the comment: Your proposal looks reasonable. Two things: - your patch should include an unit test (see Lib/test/test_file2k.py) - fileobject.c should use tabs for indentation, not spaces And you're right, py3k doesn't have this problem. -- nosy: +pitrou, tim_one versions: -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7079 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: Hello There has been a number of discussions about bdist_deb, and some code too. I don’t have links handy, unfortunately, but I remember a conclusion that was: Don’t. Debian packages are best made by Debian tools, which go to great lengths to comply with Debian Policy, work together, and are frequently updated. On the Distutils(2) site, the most we can do would be a bdist_dsc command that produces a special file which is used by debianizing tools. A key thing to remember is that .deb is not just a file format, it’s the embodiment of a Policy (the real value of Debian is its policy, not its package manager—a nice technical side effect), and as such, best handled by Debian tools. Disclaimers: I’ve not been following packaging discussions for long, these lines are a summary of other people’s thoughts, I’m not a Debian developer or maintainer. Cheers -- components: +Distutils2 -Distutils nosy: +merwok versions: +Python 2.5, Python 2.6, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: There are really two aspects of this patch. At the moment, I'm less interested in bdist_deb than I am in the 'debianize' (i.e. dh_make) functionality. I think 'python setup.py debianize' (or whatever) would be a nice way to jump start a debian/ directory from the available metadata. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Éric Araujo mer...@netwok.org added the comment: Why not use Debian’s dh_make? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1404] warnings module bug: BytesWarning: str() on a bytes instance
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1404 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1601 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3947] configure --with-threads on cygwin = crash on thread related tests
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3947 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5249] Fix strftime on windows.
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5249 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5273] 3.0.1 crashes in unicode path
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5273 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5334] array.fromfile() fails to insert values when EOFError is raised
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5334 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6150] test_unicode fails in wide unicode build
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6150 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6453] Improve bool TypeError message
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6453 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7540] urllib2 request does not update content length after new add_data
Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7540 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1054967] bdist_deb - Debian packager
Barry A. Warsaw ba...@python.org added the comment: That's essentially what I want, except I want to feed dh_make some better defaults based on metadata that already lives in setup.py. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1054967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7027] test_io.py: codecs.IncrementalDecoder is sometimes None
STINNER Victor victor.stin...@haypocalc.com added the comment: test_io and test_codecs didn't fail in the last build of x86 Tiger 2.6 and x86 Windows7 2.6. I suppose that the issue is now closed. Repopen the issue if it's not the case. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8550] Expose SSL contexts
New submission from Antoine Pitrou pit...@free.fr: We should expose SSL contexts at the Python level, and rework SSL sockets to use those objects internally (rather than creating their own private context). It would allow to: - specify the various options iteratively, rather than having to dump them all in the wrap_socket() arguments - add methods to query information about the current options, key/cert, etc. - solve issue3823 (you can build the context first, passing it the key/cert info, then drop privileges before creating any sockets) - more easily share and reuse configuration information - possibly add more powerful functionality such as sessions The way I see it, the existing wrap_socket() module-level function would be kept for compatibility; context objects would expose their own wrap_socket() method, without all the arguments of course. -- components: Library (Lib) messages: 104359 nosy: giampaolo.rodola, janssen, pitrou priority: normal severity: normal stage: needs patch status: open title: Expose SSL contexts type: feature request versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8550] Expose SSL contexts
Jean-Paul Calderone exar...@twistedmatrix.com added the comment: For reference: http://pyopenssl.sourceforge.net/pyOpenSSL.html/openssl-context.html http://www.heikkitoivonen.net/m2crypto/api/M2Crypto.SSL.Context%27.Context-class.html and `man -k SSL_CTX_` -- nosy: +exarkun ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8546] The parameter buffering in _pyio.open doesn't work the same as in the builtin open
Benjamin Peterson benja...@python.org added the comment: Fixed in r80544. -- nosy: +benjamin.peterson resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1284316] Win32: Security problem with default installation directory
Fran Rogers f...@dumetella.net added the comment: I'd like to concur that Python should install to %ProgramFiles% by default. The root-directory default is particularly anomalous on 64-bit Windows, where you have separate 64- and 32-bit Program Files directories; if I have a Python installation in C:\Python26, is it amd64 Python or x86 Python? If I want to install both (since many packages don't yet support amd64), which one should I install to \Python26 and which should I rename? As mel's post above (2005-11-15 11:39) points out, installing to C:\ is comparable to installing to /python2.6 on a Unix box; it's nonstandard, inelegant, and prone to ACL problems like the one this bug was opened for. If convenience on the command line (for non-power-users unfamiliar with %Path%) is the concern, a better solution would be a checkbox in the installer to add the new Python to the system %Path%. -- nosy: +fran.rogers ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1284316 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4870] ssl module is missing SSL_OP_NO_SSLv2
Antoine Pitrou pit...@free.fr added the comment: Here is an updated patch for py3k (the previous one didn't apply cleanly). -- Added file: http://bugs.python.org/file17112/sslopts2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3596] Provide a way to disable SSLv2 (or better yet, disable by default)
Antoine Pitrou pit...@free.fr added the comment: Someone else requested it and even provided a patch. See you on issue4870. -- resolution: out of date - duplicate status: pending - closed superseder: - ssl module is missing SSL_OP_NO_SSLv2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3596 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2550] SO_REUSEADDR doesn't have the same semantics on Windows as on Unix
Antoine Pitrou pit...@free.fr added the comment: This is now fixed, right? Personal experience as well as buildbot behaviour seems to show that parallel test execution (either through -j, or by running several test suites at the same time) works ok. -- nosy: +exarkun, pitrou resolution: accepted - fixed stage: unit test needed - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs
Changes by Fredrik Håård fredrik.ha...@gmail.com: -- nosy: +fredrik.haard ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6662 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8086] ssl.get_server_certificate new line missing
Antoine Pitrou pit...@free.fr added the comment: This looks reasonable enough. -- nosy: +pitrou stage: unit test needed - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6662] HTMLParser.HTMLParser doesn't handle malformed charrefs
Fredrik Håård fredrik.ha...@gmail.com added the comment: Is there a reason for HTMLParser to treat anything that does not match the regex '#\d+;' as a charref? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6662 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
