[Python-Dev] Issue 24285: regression for importing extensions in packages

Nathaniel Smith njs at pobox.com
Thu May 28 07:19:03 CEST 2015

On Wed, May 27, 2015 at 9:54 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 28 May 2015 at 14:30, Larry Hastings <larry at hastings.org> wrote:
> > On 05/27/2015 07:51 PM, Ned Batchelder wrote:
> >
> > This issue has been fixed, but a day or two late for 3.5b1.  It prevents
> > loading the coverage.py extension.  It'd be great to get a new beta release
> > soon. :)
> >
> >
> > http://legacy.python.org/dev/peps/pep-0478/
> Aye, it's the long gap from May 24 (3.5b1) to July 5 (3.5b2) that we
> were hoping to see shortened if it was possible to get the release
> team together.
> The fact folks can't currently import extension modules that aren't at
> top level is unfortunately going to limit the amount of 3.5b1 testing
> the community can do in those 6 weeks :(

Just chiming in to confirm that yep, numpy (and thus the whole
numerical stack) are also missing on 3.5b1. Of course this was filed
as a bug report on numpy :-):


I guess the good news is that people are in fact testing the beta, but
it sounds like pretty much the only code running on b1 is pure Python
code whose entire dependency chain is also pure Python code.

On the upside, compatibility between PyPy and CPython has improved greatly ;-).


Nathaniel J. Smith -- http://vorpus.org

More information about the Python-Dev mailing list