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

Nick Coghlan ncoghlan at gmail.com
Thu May 28 06:54:16 CEST 2015

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 :(

Regards, Nick.

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

More information about the Python-Dev mailing list