[issue6210] Exception Chaining missing method for suppressing context
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset b299c4f31ff2 by Nick Coghlan in branch 'default': Close issue #6210: Implement PEP 409 http://hg.python.org/cpython/rev/b299c4f31ff2 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6210 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6210] Exception Chaining missing method for suppressing context
Changes by Nick Coghlan ncogh...@gmail.com: -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6210 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12801] C realpath not used by os.path.realpath
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12801 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14082] shutil doesn't copy extended attributes
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14082 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6210] Exception Chaining missing method for suppressing context
Éric Araujo mer...@netwok.org added the comment: Thanks, I can’t wait to use that in my code! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6210 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14097] Improve the introduction page of the tutorial
Eli Bendersky eli...@gmail.com added the comment: Regarding the use of the name variable, could it be replaced by just name ? That might make sense since the error for undefined names is usually NameError. However, note that the current documentation has a /huge/ amount of mentions for variable, so we may be too late to the party. Éric - the word degenerate is considered offensive in a couple of languages I speak, but the docs are written in English, so the important point is whether this word is offensive *in English*. If not, I see no reason to drop it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14097 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
New submission from Larry Hastings la...@hastings.org: Following on from Guido's rejection of PEP 410: http://mail.python.org/pipermail/python-dev/2012-February/116837.html This bug is the proposed hammering-out space for how to preserve exact metadata for st_atime / st_mtime between os.stat and os.utime. (Yes, there's already #11457 -- but that went pretty far down the rabbit hole of Decimal. I thought maybe a fresh start would be best.) -- components: Library (Lib) messages: 154316 nosy: larry priority: normal severity: normal status: open title: os.stat and os.utime: allow preserving exact metadata type: enhancement versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
New submission from Eli Bendersky eli...@gmail.com: Element, XMLParser and TreeBuilder are types in ElementTree, but factory functions in _elementtree. The latter should be modified to be consistent with the former. -- assignee: eli.bendersky components: Library (Lib) messages: 154317 nosy: eli.bendersky, flox, scoder priority: high severity: normal stage: needs patch status: open title: _elementtree should expose types and factory functions consistently with ElementTree type: behavior versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6884] Impossible to include file in sdist that starts with 'build' on Win32
Nadeem Vawda nadeem.va...@gmail.com added the comment: For distutils2 however I have no tester and no bot, so could someone test this patch? I'll take a look at it. BTW if someone knows about a continuous integration service which provides Windows and Mac OS X VMs I’m all ears. Not sure about a CI service, but if you want Windows for your own machine I believe you can get a free MSDN subscription: http://mail.python.org/pipermail/python-committers/2011-August/001788.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6884 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Larry Hastings la...@hastings.org added the comment: Guido proposed st_atime_ns et al. I'll make an alternate proposal. I'd like to avoid tying ourselves to ns resolution. As MvL said: I don't want to deal with this issue *again* in my lifetime. If all we want is to facilitate copying the exact metadata from os.stat to os.utime, then we don't really care about conveniently modifying the timestamp. So I propose we use MvL's suggestion of a tuple of ints. Either (numerator, denominator) or (seconds, fractional_numerator, fractional_denominator). (These are mentioned in PEP 410 under the heading Tuple of ints as options A and B respectively.) Name the fields with the suffix _exact (e.g. st_mtime_exact). os.stat and its ilk produce it; os.utime and its ilk consume it. If people want to monkey with the values and do math, let 'em--consenting adults. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14123] Indicate that there are no current plans to deprecate printf-style formatting
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 80069bbae26d by Gregory P. Smith in branch '3.2': Issue #14123: Explicitly mention that old style % string formatting has caveats http://hg.python.org/cpython/rev/80069bbae26d New changeset 98a1855ebfe1 by Gregory P. Smith in branch 'default': Issue #14123: Explicitly mention that old style % string formatting has caveats but is not going away any time soon. http://hg.python.org/cpython/rev/98a1855ebfe1 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14123 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
Stefan Behnel sco...@users.sourceforge.net added the comment: Note that Element is also a factory function in lxml.etree, and people have been living with this quite happily. I don't see a reason to change either side. There is a dedicated function iselement(obj) for exactly the purpose of testing if something is an Element object. isinstance() is not the right way to do it and inheritance is not portable. (the right type to inherit from in lxml is actually called ElementBase) I'm fine with changing the other two (XMLParser and TreeBuilder), if only for consistency. Stefan -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
Eli Bendersky eli...@gmail.com added the comment: In the pydev discussion once Martin raised this problem it was agreed that this is a regression in 3.3 that should be fixed, since there is code out there that relies on subclassing Element. This would make the Python and C implementations of ET more consistent, which can't be a bad thing. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Stefan Krah stefan-use...@bytereef.org added the comment: Nick Coghlan rep...@bugs.python.org wrote: PEP section makes sense - I plan to mark PEP 3118 as Final once you commit this (or you can do that yourself, for that matter). Array features are complete except for multi-dimensional indexing and slicing. I think it would be nice to add those in a separate issue; it's not a lot of additional code and it doesn't interfere with the current code. The overall array handling scheme is sound. Life would be a bit easier if contiguity flags were a mandatory part of the Py_buffer structure that the exporter has to fill in. Then there is an open issue (#3132) for expanding the struct module syntax, where the wording in some sections of the PEP led to a bit of head-scratching. :) In another issue (#13072) the question came up whether the proposed 'u' and 'w' formats still make sense after PEP-393 (I think they do, they should map to UCS-2 and UCS-4). We need to decide what to do about 2.7 and 3.2. It's pretty difficult by now to separate the bug fixes from the features. I could follow the example of CPU manufacturers: start with the whole feature set and disable as much as possible. Another problem for 2.7 and 3.2 is that the 'B' format would still need to accept bytes instead of ints. Or can we change that as a bug fix? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Stefan Krah stefan-use...@bytereef.org added the comment: I think this issue is now superseded by #10181 and #3132. -- nosy: +skrah resolution: - duplicate stage: test needed - committed/rejected status: open - pending superseder: - Problems with Py_buffer management in memoryobject.c (and elsewhere?) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2394] [Py3k] Finish the memoryview object implementation
Changes by Stefan Krah stefan-use...@bytereef.org: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
New submission from Eli Bendersky eli...@gmail.com: I'm now carefully reading through the extending documentation pages. This issue will record various problems I find on the way, with the intention of fixing them eventually. -- assignee: eli.bendersky components: Documentation keywords: easy messages: 154325 nosy: eli.bendersky priority: low severity: normal status: open title: Corrections for the extending doc versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: extending.html has a reference to Demo/embed/demo.c which no longer exists in the source distribution -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Nick Coghlan ncogh...@gmail.com added the comment: Aw, I guess I was too optimistic in thinking this was the last gap before we could declare it Final... +1 on creating a new feature request for NumPy style multi-dimensional indexing and slicing support on memoryview (I'm assuming that's what you meant). As far as your last question goes, I'm not sure we *can* salvage this in 2.7/3.2. We do have the option of throwing our hands up in the air and saying Sorry, we couldn't figure out how to fix it without completely rewriting it. Take a look at 3.3 if you want to see how it's *supposed* to work. I hesitate to suggest this (since I'm not volunteering to do the work) but perhaps it would be worth packaging up the 3.3. memoryview and publishing it on PyPI for the benefit of 3.2 and 2.7? May also be worth bringing up on python-dev to see if anyone else has any bright ideas. Myself, I'm not seeing any real choices beyond won't fix, backport 3.3 version and remove/disable the new features, backport 3.3 version, new features and all and publish a full featured version on PyPI. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6884] Impossible to include file in sdist that starts with 'build' on Win32
Adam Groszer agros...@gmail.com added the comment: Hello, On Sun, 26 Feb 2012 03:37:06 + you wrote: BTW if someone knows about a continuous integration service which provides Windows and Mac OS X VMs I’m all ears. ZTK (Zope toolkit) ended up with renting a windows (server) VM. http://winbot.zope.org/ There we run a buildbot that does the windows releases of some packages (zope.interface, zope.proxy, etc) and runs the tests. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6884 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
Changes by Florent Xicluna florent.xicl...@gmail.com: -- nosy: +effbot ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14107] Debian bigmem buildbot hanging in test_bigmem
Charles-François Natali neolo...@free.fr added the comment:
Thread 0x2ba588709700:
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/support.py,
line 1168 in consumer
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/threading.py, line
682 in run
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/threading.py, line
729 in _bootstrap_inner
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/threading.py, line
702 in _bootstrap
Current thread 0x2ba57b2d4260:
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/support.py,
line 1198 in stop
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/support.py,
line 1240 in wrapper
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/case.py,
line 385 in _executeTestPart
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/case.py,
line 440 in run
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/case.py,
line 492 in __call__
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/suite.py,
line 105 in run
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/suite.py,
line 67 in __call__
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/suite.py,
line 105 in run
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/suite.py,
line 67 in __call__
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/unittest/runner.py,
line 168 in run
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/support.py,
line 1369 in _run_suite
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/support.py,
line 1403 in run_unittest
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/test_bigmem.py,
line 1252 in test_main
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/regrtest.py,
line 1221 in runtest_inner
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/regrtest.py,
line 907 in runtest
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/regrtest.py,
line 710 in main
File
/var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/test/__main__.py,
line 13 in module
File /var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/runpy.py,
line 73 in _run_code
File /var/tmpfs/martin.vonloewis/3.x.loewis-parallel2/build/Lib/runpy.py,
line 160 in _run_module_as_main
There's a problem with the _file_watchdog thread:
if the pipe gets full (because the consumer thread doesn't get to run
often enough), the watchdog thread will block on the write() to the
pipe.
Then, the main thread tries to stop the watchdog:
static void
cancel_file_watchdog(void)
{
/* Notify cancellation */
PyThread_release_lock(watchdog.cancel_event);
/* Wait for thread to join */
PyThread_acquire_lock(watchdog.running, 1);
PyThread_release_lock(watchdog.running);
/* The main thread should always hold the cancel_event lock */
PyThread_acquire_lock(watchdog.cancel_event, 1);
}
The `cancel_event` lock is released, but the watchdog thread is stuck
on the write().
The only thing that could wake it up is a read() from the consumer
thread, but the main thread - the one calling cancel_file_watchdog()
- blocks when acquiring the `running` lock: since the GIL is not
released, the consumer thread can't run, so it doesn't drain the pipe,
and game over...
/* We can't do anything if the consumer is too slow, just bail out
*/
if (write(watchdog.wfd, (void *) x, sizeof(x)) sizeof(x))
break;
if (write(watchdog.wfd, data, data_len) data_len)
break;
AFAICT, this can't happen, because the write end of the pipe is not in
non-blocking mode (which would solve this issue).
Otherwise, there are two things I don't understand:
1. IIUC, the goal of the watchdog thread is to collect memory
consumption in a timely manner: that's now the case, but since the
information is printed in a standard thread, it doesn't bring any improvement
(because it can be delayed for arbitrarily long), or am I
missing something?
2. instead of using a thread and the faulthandler infrastructure to run
GIL-less, why not simply use a subprocess? It could then simply
parse /proc/PID/statm at a regular interval, and print stats to
stdout. It would also solve point 1.
--
nosy: +neologix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14107
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
Stefan Behnel sco...@users.sourceforge.net added the comment: For the record, the relevant mailing list discussion can be found here: http://thread.gmane.org/gmane.comp.python.devel/129429/focus=129794 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14007] xml.etree.ElementTree - XMLParser and TreeBuilder's doctype() method missing
Florent Xicluna florent.xicl...@gmail.com added the comment: the class versus factory issue is gone to issue 14128. The current issue is only about the doctype() method missing in the C implementation. I propose to drop this deprecated method from the Python version, instead of implementing the deprecated method in the C version. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14007 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13238] Add shell command helpers to subprocess module
Nick Coghlan ncogh...@gmail.com added the comment: For a different take on this concept: http://julialang.org/manual/running-external-programs/ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13238 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14007] xml.etree.ElementTree - XMLParser and TreeBuilder's doctype() method missing
Eli Bendersky eli...@gmail.com added the comment: Florent, The deprecation should be probably raised separately on pydev. From the recent discussions on this and similar topics, I doubt that removal of these methods will be accepted. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14007 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Martin v. Löwis mar...@v.loewis.de added the comment: OTOH, it seems that Guido is very much in favor of hard-coding ns resolution in the API, claiming that expectations of even finer resolution are academic. While I still disagree (the *very* same argument was brought up for ms resolution ten years ago), I think that practicality beats purity here: people apparently can deal with an fixed scale much better than with a floating one. So it may be better to meet the apparent intuition of the majority than follow the purity route. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14107] Debian bigmem buildbot hanging in test_bigmem
Charles-François Natali neolo...@free.fr added the comment: 1. IIUC, the goal of the watchdog thread is to collect memory consumption in a timely manner: that's now the case, but since the information is printed in a standard thread, it doesn't bring any improvement (because it can be delayed for arbitrarily long), or am I missing something? Scratch that. It does bring an improvement for a post facto analysis (I thought at first it was used in a pseudo-realtime way). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14107 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14130] memoryview: add multi-dimensional indexing and slicing
Changes by Stefan Krah stefan-use...@bytereef.org: -- assignee: skrah nosy: ncoghlan, pitrou, pv, skrah, teoliphant priority: normal severity: normal stage: needs patch status: open title: memoryview: add multi-dimensional indexing and slicing type: enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14130 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14130] memoryview: add multi-dimensional indexing and slicing
New submission from Stefan Krah stefan-use...@bytereef.org: The PEP-3118 authors originally planned to have support for multi-dimensional indexing and slicing in memoryview. Since memoryview now already has the capabilities of multi-dimensional list representations and comparisons, this would be a nice addition to the feature set. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14130 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14130] memoryview: add multi-dimensional indexing and slicing
Changes by Stefan Krah stefan-use...@bytereef.org: -- components: +Interpreter Core versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14130 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1116520] Prefix search is filesystem-centric
Nick Coghlan ncogh...@gmail.com added the comment: Yeah, I'm pretty sure the bootstrap mechanism needs to be able to get hold of os.py directly so it can be injected into the importlib._bootstrap namespace. However, it may be worth figuring out and documenting the bare minimum that has to exist on the filesystem in order for importlib to get going. It's even possible that Brett freezes enough into the interpreter binary that the required set has shrunk to zero. -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1116520 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14007] xml.etree.ElementTree - XMLParser and TreeBuilder's doctype() method missing
Florent Xicluna florent.xicl...@gmail.com added the comment: I understand the point about compatibility. However it is slightly different here, because the method is already deprecated in Python 2.7 and 3.2, with a warning in the documentation and a DeprecationWarning at runtime. This method was never available in the C version, and the documentation is clear about the recommended way of writing a custom doctype handler. Arguably, it is not the most popular feature of ElementTree. I am not opposed to adding the deprecated method in the C implementation, but it will need someone to do the patch, taking care of raising the deprecation warning correctly, and taking care of the case where XMLParser is subclassed. Is it worth the hassle? Please not that contrary to what is stated in the first message (msg153328), the doctype() method is not defined on the default TreeBuilder (Python) class. The documentation suggests to add it on custom TreeBuilder implementations. -- priority: high - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14007 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14131] test_threading failure on WIndows 7 3.x buildbot
New submission from Nick Coghlan ncogh...@gmail.com: http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.x/builds/4458/steps/test/logs/stdio Appears to be new, but also isn't obviously related to any recent checkins that I noticed. (the Win7 buildbot for trunk isn't in a good place, with regular test_packaging and test_strptime values, too). -- keywords: buildbot messages: 154339 nosy: ncoghlan priority: normal severity: normal status: open title: test_threading failure on WIndows 7 3.x buildbot versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14131 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7562] Custom order for the subcommands of build
Changes by Peter Kleiweg pklei...@xs4all.nl: -- nosy: +pebbe ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7562 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8706] accept keyword arguments on all base type methods and builtins
Filip Gruszczyński grusz...@gmail.com added the comment: I don't know if this is exactly what you want, but this is an early patch. -- keywords: +patch nosy: +gruszczy Added file: http://bugs.python.org/file24644/8706.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8706 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: in this case, nothing more than every Python object contains There's a grammar error lurking somewhere in there... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: A PyObject is not a very magnificent object - it just contains the refcount and a pointer to the object’s “type object”. Too chatty and should be replaced by a more pragmatic explanation, or shortened. -- nosy: +docs@python ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14007] xml.etree.ElementTree - XMLParser and TreeBuilder's doctype() method missing
Florent Xicluna florent.xicl...@gmail.com added the comment: This last feature (doctype handler on custom TreeBuilder) does not have tests... So, it is certainly broken with the C implementation. -- stage: needs patch - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14007 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: This is not strictly in the extending doc, but linked from it: http://docs.python.org/dev/c-api/type.html#PyType_GenericNew The PyType_GenericNew API function is not documented -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14107] Debian bigmem buildbot hanging in test_bigmem
Antoine Pitrou pit...@free.fr added the comment: /* We can't do anything if the consumer is too slow, just bail out */ if (write(watchdog.wfd, (void *) x, sizeof(x)) sizeof(x)) break; if (write(watchdog.wfd, data, data_len) data_len) break; AFAICT, this can't happen, because the write end of the pipe is not in non-blocking mode (which would solve this issue). I think my original plan was to put it in non-blocking mode, but I must have forgotten in the end. 2. instead of using a thread and the faulthandler infrastructure to run GIL-less, why not simply use a subprocess? It could then simply parse /proc/PID/statm at a regular interval, and print stats to stdout. It would also solve point 1. I can't think of any drawback off the top of my head, so that sounds reasonable. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14107 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: Let’s expend Typo -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: The new method calls the tp_alloc slot to allocate memory tp_alloc needs formatting here, similarly to the way it's done in other places -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: Noddy_name in the full code listing (included from noddy2.c) is different from the Noddy_name that is actually explained later -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14129] Corrections for the extending doc
Eli Bendersky eli...@gmail.com added the comment: but in this cased Typo [this and the past couple of comments refer to the newtypes.html doc] -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14129 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14131] test_threading failure on WIndows 7 3.x buildbot
Stefan Krah stefan-use...@bytereef.org added the comment: Strange, I can't reproduce this on Windows 7 with exactly the same command line: python_d -Wd -E -bb ../lib/test/regrtest.py -uall -rwW -n -r --randseed=8022149 -- nosy: +skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14131 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14131] test_threading failure on WIndows 7 3.x buildbot
Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: +db3l ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14131 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14131] test_threading failure on WIndows 7 3.x buildbot
Nadeem Vawda nadeem.va...@gmail.com added the comment: This is rather curious. It looks like the assertion includes a (generous) fudge factor in case the timing code is inaccurate, but then the actual time taken is *just* short enough to make it fail. (the Win7 buildbot for trunk isn't in a good place, with regular test_packaging and test_strptime values, too). I can't find any recent failures of test_packaging; do you mean test_imp? I've opened issue 14113 for the test_strptime failures; it looks like something's forgetting (or stripping off) a leading zero somewhere. -- components: +Tests nosy: +nadeem.vawda stage: - needs patch type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14131 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14085] PyUnicode_WRITE: comparison is always true warnings
Florent Xicluna florent.xicl...@gmail.com added the comment: Same on OSX, building trunk (3.3.0a0) $ uname -v Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 $ gcc --version i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3) $ ./configure MACOSX_DEPLOYMENT_TARGET=10.8 --with-pydebug (...) $ make -s -j12 (...) Objects/unicodeobject.c: In function ‘PyUnicode_FromFormatV’: Objects/unicodeobject.c:2729: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:2729: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:2729: warning: comparison is always true due to limited range of data type Python/import.c: In function ‘make_compiled_pathname’: Python/import.c:981: warning: comparison is always true due to limited range of data type Python/import.c:981: warning: comparison is always true due to limited range of data type Python/import.c:981: warning: comparison is always true due to limited range of data type Python/import.c:987: warning: comparison is always true due to limited range of data type Python/import.c:987: warning: comparison is always true due to limited range of data type Python/import.c:987: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c: In function ‘PyUnicode_DecodeUTF16Stateful’: Objects/unicodeobject.c:5525: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5525: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5526: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5526: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5528: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5528: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5529: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:5529: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c: In function ‘PyUnicode_DecodeASCII’: Objects/unicodeobject.c:6929: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:6929: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:6929: warning: comparison is always true due to limited range of data type Python/formatter_unicode.c: In function ‘fill_number’: Python/formatter_unicode.c:561: warning: comparison is always true due to limited range of data type Python/formatter_unicode.c:561: warning: comparison is always true due to limited range of data type Python/formatter_unicode.c:561: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c: In function ‘unicode_repr’: Objects/unicodeobject.c:12325: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12325: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12325: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12326: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12326: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12326: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12344: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12344: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12344: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12345: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12345: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12345: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12351: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12351: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12351: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12352: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12352: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12352: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12353: warning: comparison is always true due to limited range of data type Objects/unicodeobject.c:12353: warning: comparison is always true due to limited
[issue14107] Debian bigmem buildbot hanging in test_bigmem
Charles-François Natali neolo...@free.fr added the comment: I think my original plan was to put it in non-blocking mode, but I must have forgotten in the end. Here's a patch. I can't think of any drawback off the top of my head, so that sounds reasonable. I'll try to write up a patch (I have only 1.2GB RAM, so it won't be easy to test :-). -- keywords: +patch Added file: http://bugs.python.org/file24645/mem_watchdog_nonblock.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14107 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14080] Sporadic test_imp failure
Stefan Krah stefan-use...@bytereef.org added the comment: So the test needs to be fixed to call importlib.invalidate_caches() after creating the module. That works. With issue14080.diff I can run the failing combination without problems: $ ./python -m test test_sqlite test_imp [1/2] test_sqlite test_sqlite skipped -- No module named '_sqlite3' [2/2] test_imp 1 test OK. 1 test skipped: test_sqlite Those skips are all expected on linux. [111339 refs] Is invalidate_caches() a transitional measure until importlib is fully integrated? -- keywords: +patch Added file: http://bugs.python.org/file24646/issue14080.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14080 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14085] PyUnicode_WRITE: comparison is always true warnings
Changes by Florent Xicluna florent.xicl...@gmail.com: -- assignee: ronaldoussoren - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14085 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
R. David Murray rdmur...@bitdance.com added the comment: Is it totally insane to think about using a float subclass with an additional attribute instead of a tuple? -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14132] Redirect is not working correctly in urllib2
New submission from Ján Janech jan...@kios.sk: When only the query string is sent by the server as the redirect url, urllib2 redirects to incorrect address. Error is occuring on the page http://kniznica.uniza.sk/opac. Server sends only the query string part of the uri in the Location header (ie. ?fs=04D07295D4434730A51C95A9F1727373fn=main). Path is then incorrectly stripped from the original url, and urllib2 redirects to http://kniznica.uniza.sk/?fs=04D07295D4434730A51C95A9F1727373fn=main. The error was introduced in the fix of the issue #2464. I think, the attached patch is fixing the error (it is working for me). -- components: Library (Lib) files: urllib2_redirect_fix.patch keywords: patch messages: 154356 nosy: janik priority: normal severity: normal status: open title: Redirect is not working correctly in urllib2 type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file24647/urllib2_redirect_fix.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14132 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14132] Redirect is not working correctly in urllib2
Ján Janech jan...@kios.sk added the comment: I forgot to mention that the correct url in the example would be http://kniznica.uniza.sk/opac?fs=04D07295D4434730A51C95A9F1727373fn=main. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14132 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14132] Redirect is not working correctly in urllib2
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti, facundobatista, gregory.p.smith, orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14132 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
New submission from Benjamin Peterson benja...@python.org: It uses a __suppress_context__ attribute rather than the whole Ellipsis mess. -- components: Interpreter Core files: pep409.patch keywords: patch messages: 154358 nosy: benjamin.peterson, ncoghlan priority: normal severity: normal status: open title: improved PEP 409 implementation versions: Python 3.3 Added file: http://bugs.python.org/file24648/pep409.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Antoine Pitrou pit...@free.fr added the comment: I don't think it has to be a __special__ attribute. suppress_context would probably be fine. Also, instead of looking up the attribute in the dict, why not have a dedicated C member? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13224] Change str(x) to return only the (qual)name for some types
Guido van Rossum gu...@python.org added the comment: Not 100% sure what you're asking. Is your specific question whether it is okay that str(Counter.update) returns 'Counter.update'? Yes, it is. Same for Top.Nested.method. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13224 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14116] Lock.__enter__() method returns True instead of self
sbt shibt...@gmail.com added the comment: IIUC returning True is not incorrect, only useless. In the stdlib I usually see “with lock:”. Can you tell what is the use case for accessing the condition object inside the context block? Does it apply only to Condition or also to *Lock and Semaphore? I was going to do something like with Condition() as c: Thread(target=foo, args=(c,...)).start() c.wait_for(...) But I will agree that I don't have a compelling use case. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14116 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Guido van Rossum gu...@python.org added the comment: @RDM: yes, that's insane for this purpose. The size of the solution doesn't match the size of the problem (the problem is non-existent for most people). @Larry: That seems unnecessarily general. I take full responsibility for fixing the precision at ns. And note that I *am* giving you a way out -- I'm establishing a clear pattern, and if someone really, desperately wants ps or fs, it's completely obvious how to change the API again. But I bet you a case of beer that won't happen in our lifetimes (or in Benjamin's). So the dynamic precision is just unnneeded complexity. -- nosy: +gvanrossum ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Larry Hastings la...@hastings.org added the comment: I suggest that publishing nanoseconds as a plain int would be a nasty API. Consider what it would do to os.utime: if isinstance(mtime, int): # must be st_mtime_ns, it's in nanoseconds, use as-is value = mtime else: assert isinstance(mtime, float) # must be st_mtime, it's in seconds, multiply by a billion value = mtime * 10 Have we ever published an API that treated a parameter as two wildly different numbers based solely on whether the parameter was an int or a float? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14113] Failure in test_strptime on Windows
Stefan Krah stefan-use...@bytereef.org added the comment:
It looks like test_locale from test_format.py changes the locale on Windows:
import time
magic_date = (1999, 3, 17, 22, 44, 55, 2, 76, 0)
time.strftime(%c,
magic_date)
'03/17/99 22:44:55'
import locale
locale.getdefaultlocale()
('en_US', 'cp1252')
time.strftime(%c, magic_date)
'03/17/99 22:44:55'
oldloc = locale.setlocale(locale.LC_ALL, '')
oldloc
'English_United States.1252'
time.strftime(%c, magic_date)
'3/17/1999 10:44:55 PM'
locale.setlocale(locale.LC_ALL, oldloc)
'English_United States.1252'
time.strftime(%c, magic_date)
'3/17/1999 10:44:55 PM'
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14113
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Larry Hastings la...@hastings.org added the comment: (D'oh. My pseudo-code should have said value = int(mtime * 10) for that second assignment. Hopefully my point was still clear.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Antoine Pitrou pit...@free.fr added the comment: How about a separate float attribute for the fractional part (in seconds)? This gives a femtosecond precision (assuming a 50 bits mantissa). The utime() could accept a (integral part, fractional part) tuple to set a timestamp without losing bits. (PHP does something similar, but badly, with its microtime() function: http://www.php.net/manual/en/function.microtime.php) -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Larry Hastings la...@hastings.org added the comment: @pitrou: What would that look like when passed in to os.utime? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Antoine Pitrou pit...@free.fr added the comment:
st = os.stat('LICENSE')
st.st_mtime
1330108216.7984242
st.st_mtime_frac
0.798424152
tup = st.st_mtime, st.st_mtime_frac
os.utime('LICENSE', (tup, tup))
Of course, the fact that utime takes a (atime, mtime) tuple makes this a bit
cumbersome.
When passed a tuple, utime would ignore the fractional part of the first
element.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14127
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14107] Debian bigmem buildbot hanging in test_bigmem
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 52dc4fcd0d6f by Charles-François Natali in branch 'default': Issue #14107: test: Fix a deadlock involving the memory watchdog thread. http://hg.python.org/cpython/rev/52dc4fcd0d6f -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14107 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1116520] Prefix search is filesystem-centric
Brett Cannon br...@python.org added the comment: Importlib actually requires no files from disk; everything that is required for importlib are built-in modules or are constants in importlib itself (e.g. os.sep). So technically this should be doable since my bootstrap work freezes importlib itself. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1116520 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14080] Sporadic test_imp failure
Brett Cannon br...@python.org added the comment: importlib.invalidate_caches() would become a permanent thing if the directory listdir cache approach stays and importlib gets bootstrapped. But it would be made more general to work for any and all loaders and not be specific to importlib (e.g. 3rd-party importers would also get cleared). It's an unfortunate side-effect of mtime of directories not being granular enough. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14080 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14080] Sporadic test_imp failure
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 1d7472b015f0 by Antoine Pitrou in branch 'default': Issue #14080: fix sporadic test_imp failure. Patch by Stefan Krah. http://hg.python.org/cpython/rev/1d7472b015f0 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14080 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Benjamin Peterson benja...@python.org added the comment: __suppress_context__ parallels with __cause__ and __context__. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14080] Sporadic test_imp failure
Antoine Pitrou pit...@free.fr added the comment: Thanks for diagnosing this :) -- assignee: brett.cannon - resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14080 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14113] Failure in test_strptime on Windows
Stefan Krah stefan-use...@bytereef.org added the comment: Attached a fix that is tested on Windows. -- keywords: +patch Added file: http://bugs.python.org/file24649/issue14113.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14113 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14128] _elementtree should expose types and factory functions consistently with ElementTree
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14113] Failure in test_strptime on Windows
Antoine Pitrou pit...@free.fr added the comment: Patch works under Linux here. -- nosy: +haypo, loewis, pitrou stage: needs patch - commit review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14113 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8706] accept keyword arguments on all base type methods and builtins
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8706 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13520] Patch to make pickle aware of __qualname__
Changes by Łukasz Langa luk...@langa.pl: -- nosy: +lukasz.langa ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13520 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Martin v. Löwis mar...@v.loewis.de added the comment: I suggest that publishing nanoseconds as a plain int would be a nasty API. Consider what it would do to os.utime: No, it wouldn't. Please re-read Guido's proposal. If you want to specify nanoseconds, you have to pass the ns= parameter. My only quibble with the specific spelling is that it invokes Godwin's law (but I can live that that as a theoretical concern, also). Have we ever published an API that treated a parameter as two wildly different numbers based solely on whether the parameter was an int or a float? No, and Guido is on the record for objecting such APIs. Hence the keyword parameter. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Guido van Rossum gu...@python.org added the comment: Thanks Martin. I'd be happy with nsec instead of ns. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8706] accept keyword arguments on all base type methods and builtins
Filip Gruszczyński grusz...@gmail.com added the comment: With tests. -- Added file: http://bugs.python.org/file24650/8706_2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8706 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Benjamin Peterson benja...@python.org added the comment: Here's a patch which doesn't use the dict. -- Added file: http://bugs.python.org/file24651/pep409.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14097] Improve the introduction page of the tutorial
Terry J. Reedy tjre...@udel.edu added the comment:
In English, calling someone or something 'degenerate' is a major insult. In
means that x is not really human or what it seems or what it was. I remember
being initially startled or puzzled at the mathematical usage, but it actually
is similar, just without the strong insult. A line is a degenerate parabola; a
line segment is a degenerate ellipse; crossed lines constitute a degenerate
hyperbola; a line segment and a point on the segment constitute a degenerate
triangle. There are all limit cases, but they are simplified 'degenerated'
limit cases that lack the curvature or dimensionality of the members of the
sets that they are limits of. Note that straight lines are only degenerate as a
limit of parabolas; they are fine figures in their only right.
0/0 as the limit of 0/x for small x is degenerate in that it looses the
essential property of being a well defined real number.
'Degenerate' should not be casually applied to limits, edge cases, corner
cases, or oddball cases in general. One could claim that empty counts and
collections, including sequences, are 'degenerate' limits in that they loose
the 'essential' property of somethingness. But if one means that, then they
should be denied existence, as was done for 0 and empty sets, or put in
separate classes. (For 0 and {}, there really is a sense of insult that does
not apply to lines. We still see it with 'imaginary' numbers.) By including 0
and empty collections in their respective classes, Python denies that they are
degenerate. So I do not think any slice should be called 'degenerate'.
Certainly, the contrast between all slices working and only some indexes
working has nothing to do with 'degeneracy'.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14097
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14097] Improve the introduction page of the tutorial
Terry J. Reedy tjre...@udel.edu added the comment: I think we should feel free to change 'variable' to 'name', especially in the Intro, if it can be done gracefully in context. In my experience with python-list, the former seems a source of confusion for Python newbies. I try to avoid it when writing about Python. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14097 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Larry Hastings la...@hastings.org added the comment: My mistake! That ought to teach me to bound out of bed Sunday morning with my brilliant realization. (But it probably won't.) I volunteer to implement this, with the new custom class for the os.stat object. I'll have it done no later than the PyCon sprints next month. For the record, I actually prefer ns. s is the SI standard abbreviation for second (as is n for nano-): http://en.wikipedia.org/wiki/International_System_of_Units#Units_and_prefixes If we're going to abbreviate, I think it's reasonable to go with their standard. But I'm willing to be overridden. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13521] Make dict.setdefault() atomic
Filip Gruszczyński grusz...@gmail.com added the comment: Fixed both issues. -- Added file: http://bugs.python.org/file24652/13521_27_4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13521 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14131] test_threading failure on WIndows 7 3.x buildbot
Nick Coghlan ncogh...@gmail.com added the comment: Re: test_packaging: my mistake, the problem was actually test_package__file__ in test_imp (and Antoine already fixed it - there were some caches that weren't getting cleared properly: #14080) The last Win7 test run was green, so we may have to write this one up as a weird glitch. I'd say we leave it for a week or so, then close it if it doesn't happen again. -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14131 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14006] Improve the documentation of xml.etree.ElementTree
Leon Matthews pyt...@lost.co.nz added the comment: Thank you Éric and Ezio. I'll produce a patch to convert the javadoc to docstrings this week, then submit it here. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Nick Coghlan ncogh...@gmail.com added the comment: I don't consider using Ellipsis as a sentinel value a mess. If you don't like the PEP's solution, take it up with Guido. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Benjamin Peterson benja...@python.org added the comment: Maybe it's not awful, but why is this not a cleaner solution? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14127] os.stat and os.utime: allow preserving exact metadata
Martin v. Löwis mar...@v.loewis.de added the comment: Let's go with ns= them. It's also what POSIX uses (although I initially had problems parsing futimens, reading it as foo-timen-z, when it really is eff-youtime-en-es) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14127 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14109] test_lib2to3: output that looks like a failure on Windows 7
Changes by Antoine Pitrou pit...@free.fr: -- resolution: - duplicate status: open - closed superseder: - test_all_project_files() expected failure ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14109 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13125] test_all_project_files() expected failure
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +nadeem.vawda, skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13125 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6884] Impossible to include file in sdist that starts with 'build' on Win32
Nadeem Vawda nadeem.va...@gmail.com added the comment: Well... testing distutils2 on Windows has been quite an adventure. When I ran the test suite before applying the patch, I got a bunch of failures on all of the Python versions I tested (except the ones that had issues preventing me from running the tests at all). Only one of the failures appears to be due to the current issue. A summary of the problems, broken down by Python version: [python3 branch] - 3.3/3.2: Two failures: * One in test_command_build_ext..test_finalize_options where the library search path erroneously includes some additional directories under the Python installation directory. This failure is not fixed by the patch; it continues to fail after the patch is applied. * One in test_manifest that looks like this: FAIL: test_process_template (distutils2.tests.test_manifest.ManifestTestCase) -- Traceback (most recent call last): File C:\Users\Nadeem\Code\distutils2\distutils2\tests\test_manifest.py, line 215, in test_process_template self.assertEqual(manifest.files, ['d/b.py', 'd/d/e.py']) AssertionError: Lists differ: [] != ['d/b.py', 'd/d/e.py'] This one is clearly caused by the whole directory separator regex snafu we're trying to fix. Applying the patch fixes it, and doesn't introduce any new failures. - 3.1: Same as above, plus a failure in test_util: FAIL: test_generate_setup_py (distutils2.tests.test_util.UtilTestCase) -- Traceback (most recent call last): File C:\Users\Nadeem\Code\distutils2\distutils2\tests\test_util.py, line 557, in test_generate_setup_py self.assertEqual(out, b'SPAM\n') AssertionError: b'SPAM\r\n' != b'SPAM\n' Like the test_finalize_options failure, this isn't fixed by the patch. [default branch] - 2.7: Before the tests start running, runtests.py crashes with an ImportError complaining that it can't find the winreg module. AFAIK the registry-handling module in the stdlib is called _winreg in 2.x, and was only renamed to winreg in 3.x. - 2.6: Same as 2.7. - 2.5: Twenty (20) failures, including the three I get on 3.1, some miscellaneous stuff that looks registry-related, and around a dozen errors complaining about non-ASCII characters in bdist_msi.py's copyright notice. As above, your patch fixes the one failure in test_manifest, but none of the others. - 2.4: Can't run the tests; needs Visual C++ 2003, which (AFAICT) isn't freely available. TL;DR summary: The patch itself looks good, but D2 and Windows currently don't get along at all. I'd like to file a separate bug for the unrelated failures - do I do that here, or does distutils2 have a separate bugtracker/mailing list? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6884 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Antoine Pitrou pit...@free.fr added the comment: I find this cleaner than the contrived Ellipsis as magic value solution, myself :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14133] improved PEP 409 implementation
Nick Coghlan ncogh...@gmail.com added the comment: Because you're breaking the semantics of the raise X from Y syntax. That syntax is *just* syntactic sugar for _exc = X; _exc.__cause__ = Y; raise _exc. Under PEP 409, that remains true. Your patch breaks it. If you want to change the meaning for raise X from Y, write a new PEP. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14133 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14113] Failure in test_strptime on Windows
Brett Cannon br...@python.org added the comment: Does test.support track the locale for test mutations? If not we might want to add that check w/ all of the other interpreter state checks we have. -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14113 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
