So, I'm currently trying to fix the regression in handling __class__
references in 3.3. The first step in this is unwinding the name change
for the closure reference so it goes back to using "__class__"
(instead of "@__class__") before finding a different way to fix
#12370.
As near as I can tell,
2012/5/27 Nick Coghlan :
> So, I'm currently trying to fix the regression in handling __class__
> references in 3.3. The first step in this is unwinding the name change
> for the closure reference so it goes back to using "__class__"
> (instead of "@__class__") before finding a different way to fix
Nasty! Perhaps freeze_importlib.py could be rewritten in C, so
importlib could be recompiled when the compiler changes?
Or we support bootstrapping from the source file, e.g. with an
environment variable BOOTSTRAP_PY which points to the _bootstrap.py
source.
Regards,
Martin
__
On Sat, 26 May 2012 19:31:55 -0700
"Gregory P. Smith" wrote:
>
> There is a long term caveat to the overall approach: It still leaves the
> exception details being OpenSSL specific. If someone wants to ditch
> OpenSSL and use something else such as NSS (for example) in a future _ssl
> implementa
On Sun, 27 May 2012 12:00:57 +1000
Cameron Simpson wrote:
> On 26May2012 21:28, Antoine Pitrou wrote:
> | Not only does the error string contain more valuable information (the
> | mnemonics "SSL" and "CERTIFICATE_VERIFY_FAILED" indicate, respectively,
> | in which subpart of OpenSSL and which pre
Am 27.05.2012 09:43, schrieb Nick Coghlan:
> So, I'm currently trying to fix the regression in handling __class__
> references in 3.3. The first step in this is unwinding the name change
> for the closure reference so it goes back to using "__class__"
> (instead of "@__class__") before finding a di
On Sun, 27 May 2012 10:13:17 +0200
mar...@v.loewis.de wrote:
> > Nasty! Perhaps freeze_importlib.py could be rewritten in C, so
> > importlib could be recompiled when the compiler changes?
>
> Or we support bootstrapping from the source file, e.g. with an
> environment variable BOOTSTRAP_PY which
On 27May2012 11:29, Antoine Pitrou wrote:
| On Sun, 27 May 2012 12:00:57 +1000
| Cameron Simpson wrote:
| > On 26May2012 21:28, Antoine Pitrou wrote:
| > | You'll note there is still a "Errno 5" in that error message; I don't
| > | really know what to do with it. Hard-wiring the errno attribute
Am 28.05.2012 03:55, schrieb terry.reedy:
> http://hg.python.org/cpython/rev/4a7582866735
> changeset: 77195:4a7582866735
> branch: 3.2
> parent: 77189:6737c2ca98ee
> user:Terry Jan Reedy
> date:Sun May 27 21:29:17 2012 -0400
> summary:
> Issue12510: Attempting to get
