[Python-Dev] Issue 24285: regression for importing extensions in packages (original) (raw)

Stefan Behnel stefan_ml at behnel.de
Thu May 28 05:41:44 CEST 2015

Nick Coghlan schrieb am 28.05.2015 um 05:02:

On 28 May 2015 at 12:51, Ned Batchelder 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.

+1 for a quick beta 2 from me, too (obviously). I've already seen a bug report because a Cython compiled package doesn't work in Py3.5. Having to tell them to wait a while for beta 2 is annoying and discouraging for early testers.

Stefan

More information about the Python-Dev mailing list