[issue13769] json.dump(ensure_ascii=False) return str instead of unicode

Petri Lehtinen added the comment: Fixed, thanks. -- keywords: -needs review resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue13769] json.dump(ensure_ascii=False) return str instead of unicode

Roundup Robot added the comment: New changeset a1884b3027c5 by Petri Lehtinen in branch '2.7': #13769: Enhance docs for ensure_ascii semantics in JSON decoding functions http://hg.python.org/cpython/rev/a1884b3027c5 -- nosy: +python-dev ___ Python tra

[issue12776] argparse: type conversion function should be called only once

Roundup Robot added the comment: New changeset 1b614921aefa by R David Murray in branch '3.2': #12776,#11839: call argparse type function only once. http://hg.python.org/cpython/rev/1b614921aefa New changeset 74f6d87cd471 by R David Murray in branch 'default': Merge #12776,#11839: call argparse

[issue12776] argparse: type conversion function should be called only once

R. David Murray added the comment: Thanks, Arnaud and Mike. (And Steven, of course :) -- nosy: +r.david.murray resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue11839] argparse: unexpected behavior of default for FileType('w')

Roundup Robot added the comment: New changeset 1b614921aefa by R David Murray in branch '3.2': #12776,#11839: call argparse type function only once. http://hg.python.org/cpython/rev/1b614921aefa New changeset 74f6d87cd471 by R David Murray in branch 'default': Merge #12776,#11839: call argparse

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

R. David Murray added the comment: You are welcome, and thanks for your contribution. -- components: +Library (Lib) -Tests ___ Python tracker ___

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

Daniel Wagner-Hall added the comment: Added patch for 2.7. I'll sign the contributor form just as soon as I can get to a printer. Thanks for taking me through my first contribution. -- versions: +Python 2.7 Added file: http://bugs.python.org/file27081/issue15836-2.7.patch

[issue15837] Added test to test_random.py testing Random.shuffle

R. David Murray added the comment: The patch seems to be missing. The int=int is probably some sort of micro-optimization and perhaps should be removed. -- nosy: +r.david.murray, rhettinger ___ Python tracker ___

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

Changes by R. David Murray : -- nosy: +michael.foord ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

R. David Murray added the comment: Uploading the new patch here is the correct procedure. It will automatically be uploaded to rietveld as well. If by "how" you mean how to submit a backport, just create a patch against 2.7 tip and upload it separately. Revised patch looks good. --

[issue15837] Added test to test_random.py testing Random.shuffle

New submission from Alessandro Moura: Random.shuffle does not have a test in test_random.py; the attached patch adds this test. In addition, I rewrote the documentation string for Random.shuffle, which apparently did not reflect recent changes in the code and was inconsistent with the definiti

[issue15826] Increased test coverage of test_glob.py

R. David Murray added the comment: Is test_bytes_glob_directory_with_trailing_slash unique to bytes, or should it be added to the base class instead? What would be useful as bytes-only tests, I think, would be tests of non-ascii stuff. Although that makes me wonder, do we test non-ascii unico

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

Daniel Wagner-Hall added the comment: I seem to be getting exceptions why trying to upload a new patch to rietveld, either by the web interface (in several browsers), or by upload.py - attaching new patchset here Also, if I wanted to backport to 2.7 including an isinstance(e, types.ClassType)

[issue15809] IDLE console uses incorrect encoding.

Changes by Terry J. Reedy : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue15820] Add additional info to Resources area on Dev Guide

R. David Murray added the comment: Is the :exc:`KeyboardInterrupt` line supposed to be in there? -- nosy: +r.david.murray ___ Python tracker ___ _

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

R. David Murray added the comment: I put some review comments in rietveld (you should have gotten an email). -- ___ Python tracker ___ ___

[issue15786] IDLE code completion window does not scoll/select with mouse

Changes by Terry J. Reedy : -- nosy: +serwy, terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue15780] IDLE (windows) with PYTHONPATH and multiple python versions

Changes by Terry J. Reedy : -- versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker ___ ___ Pytho

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

R. David Murray added the comment: Sounds like a reasonable suggestion. However, the patch is not valid for 2.7, since there exceptions can be old style classes. -- nosy: +r.david.murray stage: -> patch review versions: -Python 2.6, Python 2.7, Python 3.1 ___

[issue15535] Fix pickling efficiency of named tuples in 2.7.3

Raymond Hettinger added the comment: FWIW, all pickle protocol levels are affected: Point = colletions.namedtuple('Point', ['x', 'y', 'z']) for proto in range(3): pickletools.dis(dumps(Point(10, 20, 30), proto)) I'll look at the proposed fix in more detail when I get a chance -- we want to

[issue15836] unittest assertRaises should verify excClass is actually a BaseException class

New submission from Daniel Wagner-Hall: The following code in a unittest test is a no-op: self.assertRaises(lambda: 1) I would expect this to fail the test, because I naively assumed omitting the exception class would act as: self.assertRaises(BaseException, lambda: 1) verifying that *any* E

[issue15535] Fix pickling of named tuples in 2.7.3 (BUG)

Changes by Raymond Hettinger : -- assignee: -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: > Since the committed patch is already a step in that direction, > I think it now needs to be completed. It's mandatory (IMO) > that the generated files are actually used; that the generators > are not run if not needed is optional and can be fixed later. Martin:

[issue15833] most failures to write byte-compiled file no longer suppressed

Eric Snow added the comment: I was thinking along the same lines, though it might make sense for EROFS and a few others. (http://aplawrence.com/Unixart/errors.html) -- nosy: +eric.snow ___ Python tracker

[issue15835] HP-UX build needs to be tweaked to pick up PATH_MAX

New submission from Trent Nelson: Building on HP-UX with the HP ANSI C compiler: % make cc -Ae -c -O -O -I. -I./Include-DPy_BUILD_CORE -o Python/pythonrun.o Python/pythonrun.c "Python/pythonrun.c", line 805: error #2020: identifier "PATH_MAX"

[issue15748] Various symlink test failures in test_shutil on FreeBSD

Larry Hastings added the comment: Could we work around it? Ignore the length we get back from readlink() and just measure the buffer ourselves? Or, if we wanted to be *really* paranoid, write a \0 at the length they give us back and *then* strlen it. -- _

[issue15834] 2to3 benchmark not working under Python 3

Brett Cannon added the comment: On Fri, Aug 31, 2012 at 6:42 PM, Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > > Might need to let Python 3 use its stdlib copy of lib2to3. Otherwise > > will need to come up with a way to have two copies of a library, one > > for Python 2 and an

[issue15748] Various symlink test failures in test_shutil on FreeBSD

Trent Nelson added the comment: Turns out our unit test uncovered a very subtle corner-case bug in ZFS, requiring the following patch to FreeBSD: a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sa.c index 69374fb..7f61517 100644 --- a/sys/c

[issue15834] 2to3 benchmark not working under Python 3

Antoine Pitrou added the comment: > Might need to let Python 3 use its stdlib copy of lib2to3. Otherwise > will need to come up with a way to have two copies of a library, one > for Python 2 and another for Python 3, and then copy the right thing. > Maybe a lib3 directory that is only copied over

[issue15833] most failures to write byte-compiled file no longer suppressed

Brett Cannon added the comment: So it might be a change, but I don't know if I would claim it is a regression that needs changing. If you can't write bytecode files for some reason other than permissions or the file already exists then there is something wrong with your setup that you might no

[issue15834] 2to3 benchmark not working under Python 3

New submission from Brett Cannon: 2to3 isn't (ironically) translating lib2to3 so that it can run under Python 3: File "/Users/bcannon/Developer/repo/benchmarks_py3k/lib/2to3/lib2to3/fixes/fix_operator.py", line 89, in _check_method method = getattr(self, "_" + results["method"][0].value.en

[issue15826] Increased test coverage of test_glob.py

Alessandro Moura added the comment: Agreed, here is the patch where this is done. -- Added file: http://bugs.python.org/file27078/test_glob.patch ___ Python tracker ___ _

[issue15775] Add StopParser() to expat

Changes by Berker Peksag : -- versions: +Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue8912] `make patchcheck` should check the whitespace of .c/.h files

Chris Jerdonek added the comment: The following commit from today is related to this issue: 815b88454e3e "Remove trailing whitespace in order to silence warnings on HP-UX." -- nosy: +cjerdonek ___ Python tracker __

[issue15833] most failures to write byte-compiled file no longer suppressed

Antoine Pitrou added the comment: Raising EIO in a read-only dir sounds weird. -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs

[issue15830] make -s no longer silences output from setup.py

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

[issue15821] PyMemoryView_FromBuffer() behavior change (possible regression)

Alexander Belopolsky added the comment: Here is what I think the test case should look like (untested): static PyObject * memoryview_from_buffer_cleanup(PyObject *self, PyObject *noargs) { PyObject *b, *view = NULL; Py_buffer info; Py_ssize_t shape[3] = {2, 2, 3}; Py_ssize_t str

[issue15821] PyMemoryView_FromBuffer() behavior change (possible regression)

Alexander Belopolsky added the comment: On Fri, Aug 31, 2012 at 3:12 PM, Stefan Krah wrote: > Now I'm puzzled: I thought your goal was to preserve the implicit cleanup > from 3.2, i.e. PyBuffer_Release() is called when the managed buffer is > deallocated. > The issue that I raised in msg169472

[issue15756] subprocess.poll() does not handle errno.ECHILD "No child processes"

Gregory P. Smith added the comment: thanks! I'll take care of getting this fix in. -- assignee: -> gregory.p.smith ___ Python tracker ___ __

[issue14223] curses addch broken on Python3.3a1

Nicholas Cole added the comment: import curses def test_screen(screen): screen.addch(5,5, curses.ACS_HLINE) screen.addch(5,6, curses.ACS_HLINE) screen.refresh() curses.napms(2000) curses.wrapper(test_screen) -- ___ Python tracker

[issue14223] curses addch broken on Python3.3a1

Nicholas Cole added the comment: I'm reopening this bug because I've noticed that in Python3.3rc1, although trying to print curses.ACS_HLINE and other such characters no long cause an Exception, only blank characters are printed to the screen. Tested with both Terminal.App and xterm running un

[issue15535] Fix pickling of named tuples in 2.7.3 (BUG)

Changes by Thomas Miedema : Removed file: http://bugs.python.org/file26662/namedtuple_pickle_fix.patch ___ Python tracker ___ ___ Python-bugs-

[issue15535] Fix pickling of named tuples in 2.7.3 (BUG)

Thomas Miedema added the comment: Added a better testcase. -- title: Fix pickling of named tuples in 2.7.3 -> Fix pickling of named tuples in 2.7.3 (BUG) Added file: http://bugs.python.org/file27077/namedtuple_pickle_fix.patch ___ Python tracker

[issue14783] Make int() and str() docstrings correct

Terry J. Reedy added the comment: The large issue is documenting complex signatures that do not really fit in any of the standard one-line patterns. I was initially puzzled by Raymond describing the 3.3 line as 'confusing', but putting on 'newbie glasses' I see now that correctly parsing i

[issue15756] subprocess.poll() does not handle errno.ECHILD "No child processes"

Changes by Berker Peksag : -- versions: -Python 2.6, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15821] PyMemoryView_FromBuffer() behavior change (possible regression)

Stefan Krah added the comment: Alexander Belopolsky wrote: > I am still getting up to speed with all the changes that went in since > 3.2. I'll review your patch over the weekend. Meanwhile, I think the > goal should be that after PyMemoryview_FromBuffer(info) is called, it > should be OK to d

[issue15821] PyMemoryView_FromBuffer() behavior change (possible regression)

Alexander Belopolsky added the comment: On Fri, Aug 31, 2012 at 2:34 PM, Stefan Krah wrote: > With the ManagedBuffer, we could now write a new function that returns > a memoryview with much nicer cleanup facilities. But that doesn't help > here since we're stuck with this function for 3.3.0. > >

[issue15821] PyMemoryView_FromBuffer() behavior change (possible regression)

Stefan Krah added the comment: Alexander, your test case is brilliant and could eventually go into _testbuffer.c, but I'd prefer a simpler test case for now. :) Here's a patch that restores the info.obj cleanup facility. I intentionally did not add copying the format in order to keep the diff s

[issue14783] Update int() docstring from manual

Ezio Melotti added the comment: Here's a patch for the signature. -- assignee: -> ezio.melotti keywords: +patch stage: needs patch -> commit review Added file: http://bugs.python.org/file27075/issue14783.diff ___ Python tracker

[issue15810] assertSequenceEqual should be fired when comparing sequence subclasses

Gregory P. Smith added the comment: When we added this functionality to assertEqual we were *intentionally* conservative on when it would auto-promote to nicer equality comparison functions. It needs to behave exactly as == would in all situations. >>> (1,2,3) == [1,2,3] False We must mainta

[issue15830] make -s no longer silences output from setup.py

Ned Deily added the comment: Issue15591 perhaps? -- nosy: +ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue15832] argparse: typechecks default value too early

Steven Bethard added the comment: It's a bug, but it's already been reported in Issue 12776. There's a patch there, but someone needs to commit it. -- superseder: -> argparse: type conversion function should be called only once ___ Python tracker <

[issue15832] argparse: typechecks default value too early

Changes by Steven Bethard : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: I have opened a new issue: http://bugs.python.org/issue15833 It is a regression because in Python 3.2 all failures to open the file for writing were supressed. > But as I said: I'd also be fine with declaring this VM software > unsupported. If this work-

[issue15831] comma after leading optional argument is after bracket in docs

Ezio Melotti added the comment: I think/hope that all the APIs we have in the stdlib are sane enough to have no more than 2-3 signatures (I'm not counting optional args (at the end) here). If that's not the case we should still be able to add as many signature as we need (I don't know if Sphi

[issue14783] Update int() docstring from manual

Éric Araujo added the comment: +1! This notation helps clearing up how int, str and other constructors work. -- nosy: +eric.araujo ___ Python tracker ___ ___

[issue15831] comma after leading optional argument is after bracket in docs

Chris Jerdonek added the comment: > What's this even supposed to mean? I started wondering the same thing after I posted. :) I guess my point/question is: are there any cases where more than two signatures would be needed to account for all of the possibilities? -- __

[issue15831] comma after leading optional argument is after bracket in docs

Ezio Melotti added the comment: > 766:.. method:: window.chgat([y, x, ] [num,] attr) What's this even supposed to mean? See also #14783. -- ___ Python tracker ___ _

[issue15833] most failures to write byte-compiled file no longer suppressed

New submission from Richard Oudkerk: As discussed in http://bugs.python.org/issue15819 trying to run python built outside a read-only source directory fails for me because OSError(EIO, ...) is raised when importlib tries to write the byte compiled file. (I built python in a Linux VM usin

[issue15831] comma after leading optional argument is after bracket in docs

Chris Jerdonek added the comment: > It would be fine with me to use a double signature for these. Just an FYI that more than two signatures would be needed for cases like this: 766:.. method:: window.chgat([y, x, ] [num,] attr) -- ___ Python tracker

[issue15831] comma after leading optional argument is after bracket in docs

Ezio Melotti added the comment: > No, methods for *curses* are also corrupted. I meant the double signature support. -- ___ Python tracker ___ __

[issue15831] comma after leading optional argument is after bracket in docs

Ezio Melotti added the comment: > This is what my search for ",] " gave me It would be fine with me to use a double signature for these. Georg, do you have any opinion? (The double signature might be easier to understand, but the original issue should probably be fixed in Sphinx, even if we d

[issue15701] AttributeError from HTTPError when using digest auth

Senthil Kumaran added the comment: Okay, this is funny. first info is invoking addinfourl of urllib, which would return headers. But in urllib2, the headers are self.hdrs I would side with the documentation that info is advertised method for HTTPError object. In 2.7, I guess just docs could b

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 18:18, schrieb Eric Snow: > Doesn't EIO cover pathologies which we don't want to silence? I could see > adding EROFS though. [This should *really* be its own issue] Sure, EIO indicates normally something pathological, such as a broken cable to the

[issue15831] comma after leading optional argument is after bracket in docs

Ezio Melotti added the comment: > Does Sphinx support it for *.. function::*? I'm pretty sure it does for methods, so I don't see why it shouldn't work for functions. -- ___ Python tracker ___

[issue15831] comma after leading optional argument is after bracket in docs

Andrew Svetlov added the comment: No, methods for *curses* are also corrupted. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15815] Add numerator to ZeroDivisionError messages

Ezio Melotti added the comment: I'm not sure this is really useful. Once I know that I divided by zero and I know where the division is, I don't really care what the numerator is. Knowing the exact type of the denominator (0, 0.0, 0j) doesn't sound too useful as well -- unless you somehow ma

[issue15831] comma after leading optional argument is after bracket in docs

Andrew Svetlov added the comment: Yes, it looks like Sphinx problem. About having tho signatures for single function/method. Does Sphinx support it for *.. function::*? Pointing to anchor for first signature with adding second one somewhere in paragraph text doesn't look good. --

[issue15826] Increased test coverage of test_glob.py

Ezio Melotti added the comment: I think it would be easier to subclass GlobTests and override norm and glob there (assuming that doesn't create problems with some of the tests). -- nosy: +ezio.melotti stage: -> patch review versions: +Python 3.2, Python 3.4 ___

[issue15831] comma after leading optional argument is after bracket in docs

Chris Jerdonek added the comment: This is what my search for ",] " gave me (though the OP's print and random.seed do not show up in this list): library/curses.rst 380:.. function:: newwin([nlines, ncols,] begin_y, begin_x) 659:.. method:: window.addch([y, x,] ch[, attr]) 673:.. method:: window.

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Eric Snow added the comment: Doesn't EIO cover pathologies which we don't want to silence? I could see adding EROFS though. -- nosy: +eric.snow ___ Python tracker ___ _

[issue15832] argparse: typechecks default value too early

R. David Murray added the comment: It is possible this could be considered a feature rather than a bug :) Let's see what Steven thinks. -- nosy: +bethard, r.david.murray versions: +Python 3.2, Python 3.3, Python 3.4 ___ Python tracker

[issue15831] comma after leading optional argument is after bracket in docs

Ezio Melotti added the comment: I thought that was just a matter of finding the wrong commas and fixing them, but if they are correct in the source, then the situation might be a bit more complicated. Does this happen only with "unusual" signatures like range([start], stop [, step])? FWIW th

[issue15831] comma after leading optional argument is after bracket in docs

Chris Jerdonek added the comment: Do we know that this is easy? It might be a Sphinx issue, in which case it might not be as trivial as fixing typos. I ask because the reST file looks correct (for range() for example): .. function:: range([start,] stop[, step]) -- __

[issue15832] argparse: typechecks default value too early

New submission from Riccardo Murri: The `argparse` module (tested with 2.7, but other versions might be affected) checks the `default` value of an option too early: if the default value raises an exception, then command-line parsing stops. Consider for example the following code: ##

[issue15831] comma after leading optional argument is after bracket in docs

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15831] comma after leading optional argument is after bracket in docs

Changes by Ezio Melotti : -- keywords: +easy nosy: +ezio.melotti stage: -> needs patch versions: +Python 3.4 ___ Python tracker ___ _

[issue15831] comma after leading optional argument is after bracket in docs

New submission from Chris Jerdonek: >From d...@python.org: """ In a number of places we find documentation with optional leading arguments where the meta-notation (square brackets) are in the wrong place. For example, for range, the standard doc heading says range([start], stop [, st

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 17:32, schrieb Richard Oudkerk: >File "", line 128, in _write_atomic > OSError: [Errno 5] Input/output error: > '/mnt/hgfs/Repos/cpython-dirty/Lib/__pycache__/codecs.cpython-33.pyc.3076609376' > Aborted > > I took this to be a failure to write t

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: It looks like the code which writes the byte-compiled codes checks for and ignores PermissionError (EACCES, EPERM) and FileExistsError (EEXIST). However, for me it is EIO which is raised. -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: > Why is that? python will work just fine if it can't write pyc files. When I hacked around the _sysconfigdata.py issue, running the created python produced Fatal Python error: Py_Initialize: Unable to get the locale encoding Traceback (most recent call last)

[issue15828] imp.load_module doesn't support C_EXTENSION type

Roundup Robot added the comment: New changeset d54f047312a8 by Brett Cannon in branch 'default': Issue #15828: Don't try to close a file if imp.find_module() doesn't http://hg.python.org/cpython/rev/d54f047312a8 -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 16:40, schrieb Richard Oudkerk: > I suspect a bigger issue is the fact that *.pyc files cannot be > written to $(srcdir)/Lib/__pycache__. This means that to complete > the build, $(PYTHON_FOR_BUILD) should probably include the -B flag to > prevent i

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: > Richard: what was your use case? Building on the main host and a VM without having to commit and synchronize temporary changes. (The VM has read-only access to the host's repositories). > What steps did you take that resulted in getting typeslots.inc and

[issue15828] imp.load_module doesn't support C_EXTENSION type

Roundup Robot added the comment: New changeset 9ba57938f54d by Nick Coghlan in branch 'default': Issue #15828: Restore support for C extension modules in imp.load_module() http://hg.python.org/cpython/rev/9ba57938f54d -- nosy: +python-dev ___ Python t

[issue15828] imp.load_module doesn't support C_EXTENSION type

Nick Coghlan added the comment: Over to Georg to cherry pick this one into rc2 -- assignee: -> georg.brandl ___ Python tracker ___ __

[issue13992] Segfault in PyTrash_destroy_chain

Manu Cupcic added the comment: I am testing this patch right now. Will report back. -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue15828] imp.load_module doesn't support C_EXTENSION type

Nick Coghlan added the comment: Since I'm still up, I guess I'll check it in, then :) -- ___ Python tracker ___ ___ Python-bugs-list m

[issue15830] make -s no longer silences output from setup.py

New submission from Brett Cannon: Sometime in the last month (probably) I change has been made in either configure(.ac), Makefile.pre.in, or setup.py that is causing the -s option passed to make to not also make its way into setup.py when extensions are built. -- components: Build keyw

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 15:19, schrieb Trent Nelson: > I think I should clarify my use case that resulted in raising this > bug. > > 1. Create a fresh hg clone, say, ~/hg/cpython-3.2. > 2. Make it readonly The use case is really uncontended, and long-standing. People want

[issue14502] Document better what happens on releasing an unacquired lock

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: Well, that escalated quickly :-) I think I should clarify my use case that resulted in raising this bug. 1. Create a fresh hg clone, say, ~/hg/cpython-3.2. 2. Make it readonly: `zfs set readonly=on tank/home/cpython/hg/cpython-3.2` 3. cd /tmp/cpython-3.2-build 4.

[issue15828] imp.load_module doesn't support C_EXTENSION type

Brett Cannon added the comment: LGTM -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue15829] Threading Lock - Wrong Exception Name

R. David Murray added the comment: Please see Issue 14502. The docs probably do need clarification, but it must be done carefully. -- nosy: +r.david.murray ___ Python tracker _

[issue15828] imp.load_module doesn't support C_EXTENSION type

Nick Coghlan added the comment: I'm heading to bed, so whoever reviews this one, please feel free to add a NEWS entry and check it in :) -- ___ Python tracker ___ __

[issue15828] imp.load_module doesn't support C_EXTENSION type

Changes by Nick Coghlan : Removed file: http://bugs.python.org/file27073/issue15828_handle_extension_modules.diff ___ Python tracker ___ ___

[issue15828] imp.load_module doesn't support C_EXTENSION type

Nick Coghlan added the comment: Tweaked patch to also fix the typo in the error message -- Added file: http://bugs.python.org/file27074/issue15828_handle_extension_modules.diff ___ Python tracker _

[issue15828] imp.load_module doesn't support C_EXTENSION type

Changes by Nick Coghlan : -- nosy: +georg.brandl stage: -> commit review ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue15828] imp.load_module doesn't support C_EXTENSION type

Nick Coghlan added the comment: Patch adds test case and fix (there was simply a missing entry for C_EXTENSION/load_dynamic in the load_module if-elif chain). Also moves an imp module test from test_import to test_imp (it's the test I used as a guide to check I wasn't missing anything obvious

[issue15828] imp.load_module doesn't support C_EXTENSION type

Nick Coghlan added the comment: An even easier reproducer: >>> import imp [93559 refs] >>> details = imp.find_module("_elementtree") [93572 refs] >>> mod = imp.load_module('_elementtree', *details) Traceback (most recent call last): File "", line 1, in File "/home/ncoghlan/devel/py3k/Lib/im

  1   2   >