[issue14600] Change ImportError reference handling, naming

Éric Araujo added the comment: As was pointed on python-dev for the first commit: args = PyTuple_New(1); if (args == NULL) return NULL; kwargs = PyDict_New(); if (args == NULL) return NULL; It looks like the second block has a copy-paste typo and should check k

[issue12598] Move sys variable initialization from import.c to sysmodule.c

Nick Coghlan added the comment: It's about navigability/discovery of the source - to find out how the sys module gets initialised, you currently have to look in multiple places. The idea of the patch is to simplify that to the one logical place: sysmodule.c However, I'm not sure it's right to

[issue1615] descriptor protocol bug

Changes by Éric Araujo : -- nosy: +eric.araujo versions: +Python 3.2, Python 3.3 -Python 2.6 ___ Python tracker ___ ___ Python-bugs-lis

[issue14615] pull some import state out of the interpreter state

Martin v. Löwis added the comment: > Rather than being arbitrary, the motivation here is to limit amount > of the import state that is specific to CPython. What is gained by doing that? > Finally, modules (the biggie) is accessible as sys.modules. > importlib uses sys.modules. The C import im

[issue3561] Windows installer should add Python and Scripts directories to the PATH environment variable

Éric Araujo added the comment: A minor thing: The capitalization of the feature names is inconsistent. -- ___ Python tracker ___ ___ P

[issue14588] PEP 3115 compliant dynamic class creation

Nick Coghlan added the comment: I thought about that, and I'd prefer a dedicated dictionary to avoid questions of name conflicts. Wrapping the keyword args in a dict() call is still pretty clean: C = operator.build_class('C', (A, B), dict(metaclass=MyMeta)) -- __

[issue14590] ConfigParser doesn't strip inline comment when delimiter occurs earlier without preceding space.

Éric Araujo added the comment: I don’t remember if the doc is precise or not about this behavior, but I’m convince people used trial-and-error to see what exactly configparser would do, and rely on that knowledge know. I think I had to do that once. Thus it is not clear to me that changing

[issue14601] PEP sources not available as documented

Éric Araujo added the comment: Thanks for the report. www.python.org is not in a python-dev repository, so there is nothing the developers following bugs.python.org can do. Could you repost the problem to the pydotorg mailing list? -- nosy: +eric.araujo

[issue13476] Simple exclusion filter for unittest autodiscovery

Éric Araujo added the comment: > A -x flag would be more useful if I could specify it on the "python setup.py > tests" command line The most common distutils test command is part of setuptools, not the standard library. Other people have also written other test, tests or nosetests commands.

[issue14601] PEP sources not available as documented

Benjamin Peterson added the comment: It's fine now, anyway. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue14601] PEP sources not available as documented

Éric Araujo added the comment: How so? Links still point to the old Subversion server. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue14385] Support other types than dict for __builtins__

Antoine Pitrou added the comment: This looks fine. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue3561] Windows installer should add Python and Scripts directories to the PATH environment variable

Brian Curtin added the comment: The attached patch changes the feature text to "Add python.exe to Path". I'm not sure the word "search" adds much there anyway. An additional change here that I think would be beneficial is a better description text, immediately covering the benefit of this fea

[issue14385] Support other types than dict for __builtins__

Roundup Robot added the comment: New changeset e3ab8aa0216c by Victor Stinner in branch 'default': Issue #14385: Support other types than dict for __builtins__ http://hg.python.org/cpython/rev/e3ab8aa0216c -- nosy: +python-dev ___ Python tracker

[issue14385] Support other types than dict for __builtins__

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue4892] Sending Connection-objects over multiprocessing connections fails

Antoine Pitrou added the comment: Could you regenerate your patch now that the win32 -> _winapi changes have been applied? -- ___ Python tracker ___

[issue4892] Sending Connection-objects over multiprocessing connections fails

Changes by Antoine Pitrou : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Jesús Cea Avión added the comment: Patch ad030571e6c0 introduces a compilation warning in Python 2.7. See -- nosy: +jcea versions: +Python 2.7, Python 3.2 ___

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Jesús Cea Avión added the comment: In fact, the compilation warning seems to expose a far more serious issue. -- ___ Python tracker ___ _

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Gregory P. Smith added the comment: That warning is correct, there's a bug in the code. but given this is only a bug when PyMem_MALLOC returns NULL I do not expect this to be an issue for anyone who does not already have issues. Regardless, I'm fixing it. -- ___

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Roundup Robot added the comment: New changeset b82a471d2c5e by Gregory P. Smith in branch '2.7': Fix compiler warning related to issue #14331. harmless. http://hg.python.org/cpython/rev/b82a471d2c5e -- ___ Python tracker

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Jesús Cea Avión added the comment: "PyErr_NoMemory()" returns always NULL, but it is declared as returning "PyObject *". Could we change "return PyErr_NoMemory();" to "PyErr_NoMemory(); return NULL;"?. Maybe with some comment... A cast would silence the compiler but could be unclear. What do

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Jesús Cea Avión added the comment: Gregory patching was faster than my writing :-). Thanks for taking the effort :-). -- ___ Python tracker ___

[issue14331] Python/import.c uses a lot of stack space due to MAXPATHLEN

Gregory P. Smith added the comment: already fixed, I just manually returned NULL. :) I suppose we could change PyErr_NoMemory's definition in 3.3 to return a "void *" instead of "PyObject *" but I'd rather not. In this case the warning caused me to examine the code and determine if it was in

[issue14615] pull some import state out of the interpreter state

Brett Cannon added the comment: Eric put this in the bug tracker because I asked him to; I'm getting more emails about stuff about importlib that it's a little hard to keep track of everything. But originally this was about exposing what is left of the C-level APIs so it no longer was hidden

[issue14381] Intern certain integral floats for memory savings and performance

Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue14618] remove modules_reloading from the interpreter state

New submission from Eric Snow : Once imp.reload() is moved to imp.py, and the code is stripped from Python/import.c, we can see where modules_reloading stands. I expect that it will have become entirely superfluous at that point. -- components: Interpreter Core messages: 158691 nosy:

[issue14615] pull some import state out of the interpreter state

Eric Snow added the comment: for modules_reloading, issue14618 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue14615] pull some import state out of the interpreter state

Eric Snow added the comment: Thanks for your feedback, Martin. I'll go ahead and make a new issue for modules_reloading (and one for interp->modules when appropriate). -- resolution: -> rejected status: open -> closed ___ Python tracker

[issue14618] remove modules_reloading from the interpreter state

Eric Snow added the comment: see issue14615 for the broader picture -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue14538] HTMLParser: parsing error

Roundup Robot added the comment: New changeset 36c901fcfcda by Ezio Melotti in branch '2.7': #14538: HTMLParser can now parse correctly start tags that contain a bare /. http://hg.python.org/cpython/rev/36c901fcfcda New changeset ba4baaddac8d by Ezio Melotti in branch '3.2': #14538: HTMLParser

[issue14538] HTMLParser: parsing error

Ezio Melotti added the comment: This is now fixed, thanks for the report! Regarding the documentation feel free to open another issue, but at some point I'll probably update it anyway and/or write down somewhere what the future plans for HTMLParser and its goals. -- resolution: -> f

[issue14308] '_DummyThread' object has no attribute '_Thread__block'

cooyeah added the comment: I saw the similar problem on Ubuntu 12.04 with django development server with mediageneartor. As Dustin suggested, I don't think this is related to the "del _Thread__block" statement. I hacked the __getattribute__ of DummyThread class def __getattribute__(self,

[issue14619] Enhanced variable substitution for databases

New submission from Raymond Hettinger : I suggest adding a ?? placeholder for variable length substitutions in SQL statements: vars = 'Knight', ('Gwain', 'Gallahad', 'Lancelot'), 30 c.execute('''SELECT * FROM loyalsubjects WHERE rank = ? AND name IN (??)

[issue14591] Value returned by random.random() out of valid range

Raymond Hettinger added the comment: This needs a patch. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue14591] Value returned by random.random() out of valid range

Mark Dickinson added the comment: Here's a modification of Serhiy's patch that assures that the new state is nonzero. (Just to clarify the nonzero requirement: the MT state is formed from bit 31 of mt[0] together with all the bits of mt[i], 1 <= i < 624. At least one of these 19937 bits mu

<    1   2