Re: [Python-Dev] [Python-checkins] cpython (2.7): PDB now will properly escape backslashes in the names of modules it executes.

2011-11-18 Thread Éric Araujo
Hi Jason, > http://hg.python.org/cpython/rev/f7dd5178f36a > branch: 2.7 > user:Jason R. Coombs > date:Thu Nov 17 18:03:24 2011 -0500 > summary: > PDB now will properly escape backslashes in the names of modules it > executes. Fixes #7750 > diff --git a/Lib/test/test_pdb.p

Re: [Python-Dev] how to find the file path to an extension module at init time?

2011-11-18 Thread Stefan Behnel
Stefan Behnel, 15.11.2011 09:01: "Martin v. Löwis", 15.11.2011 01:33: An approach similar to _Py_PackageContext should be possible. Yes, and a "_Py_ModuleImportContext" would be rather trivial to do. Could that go into 3.3? If somebody contributes a patch: sure. Ok, cool. Patch(es) uploa

Re: [Python-Dev] _PyImport_FindExtensionObject() does not set _Py_PackageContext

2011-11-18 Thread Stefan Behnel
Stefan Behnel, 13.11.2011 19:48: I noticed that _PyImport_FindExtensionObject() in Python/import.c does not set _Py_PackageContext when it calls the module init function for module reinitialisation. However, PyModule_Create2() still uses that variable to figure out the fully qualified module name

[Python-Dev] Summary of Python tracker Issues

2011-11-18 Thread Python tracker
ACTIVITY SUMMARY (2011-11-11 - 2011-11-18) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open3115 ( +5) closed 22097 (+41) total 25212 (+46) Open issues wit

[Python-Dev] Committing PEP 3155

2011-11-18 Thread Antoine Pitrou
Hello, I haven't seen any strong objections, so I would like to go ahead and commit PEP 3155 (*) soon. Is anyone against it? (*) "Qualified name for classes and functions" http://www.python.org/dev/peps/pep-3155/ Thank you Antoine. ___ Python-D

Re: [Python-Dev] Committing PEP 3155

2011-11-18 Thread Barry Warsaw
On Nov 18, 2011, at 09:14 PM, Antoine Pitrou wrote: >I haven't seen any strong objections, so I would like to go ahead and >commit PEP 3155 (*) soon. Is anyone against it? > >(*) "Qualified name for classes and functions" >http://www.python.org/dev/peps/pep-3155/ I'm still not crazy about the

Re: [Python-Dev] Committing PEP 3155

2011-11-18 Thread Antoine Pitrou
On Fri, 18 Nov 2011 18:15:28 -0500 Barry Warsaw wrote: > On Nov 18, 2011, at 09:14 PM, Antoine Pitrou wrote: > > >I haven't seen any strong objections, so I would like to go ahead and > >commit PEP 3155 (*) soon. Is anyone against it? > > > >(*) "Qualified name for classes and functions" > >h

Re: [Python-Dev] Committing PEP 3155

2011-11-18 Thread Barry Warsaw
On Nov 19, 2011, at 12:54 AM, Antoine Pitrou wrote: >I've added explanations for these two points. Do they satisfy your >expectations? Yep, thanks. -Barry ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-

Re: [Python-Dev] Committing PEP 3155

2011-11-18 Thread Victor Stinner
I haven't seen any strong objections, so I would like to go ahead and commit PEP 3155 (*) soon. Is anyone against it? I'm not against it, but I have some questions. Does you a working implementing? Do you have a patch for issue #9276 using __qualname__? Maybe not a fully working patch, but a

Re: [Python-Dev] Committing PEP 3155

2011-11-18 Thread Serhiy Storchaka
19.11.11 01:54, Antoine Pitrou написав(ла): Well, the other propositions still seem worse to me. "Qualified" is reasonably accurate, and "qualname" is fairly short and convenient (I would hate to type "__qualifiedname__" or "__qualified_name__" in full). In the same vein, we have __repr__ which m