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

Nick Coghlan ncoghlan at gmail.com
Thu May 28 05:02:04 CEST 2015

On 28 May 2015 at 12:51, Ned Batchelder <ned at nedbatchelder.com> wrote:
> This issue has been fixed, but a day or two late for 3.5b1.

Aye, we only found out about the missing test case via feedback *on*
the beta. We had never needed to worry about it before, but it turns
out all our extension modules in the standard library are top level
modules and we didn't previously have an explicit test for the
submodule case :(

> It prevents
> loading the coverage.py extension.  It'd be great to get a new beta release
> soon. :)

Until your email, I hadn't fully thought through the consequences, but
the bug is actually going to block a *lot* of potential testing of the
beta release - anything that requires a C extension module that isn't
a top level module isn't going to work with 3.5b1.


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list