[Python-Dev] Issue 24285: regression for importing extensions in packages (original) (raw)
Larry Hastings larry at hastings.org
Thu May 28 07:35:24 CEST 2015
- Previous message (by thread): [Python-Dev] Issue 24285: regression for importing extensions in packages
- Next message (by thread): [Python-Dev] Issue 24285: regression for importing extensions in packages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/27/2015 08:02 PM, Nick Coghlan wrote:
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 :(
Well, certainly this sounds like something that needs to go into the regression test suite. Can someone create the issue?
... and the patch?
//arry/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150527/0615dcff/attachment.html>
- Previous message (by thread): [Python-Dev] Issue 24285: regression for importing extensions in packages
- Next message (by thread): [Python-Dev] Issue 24285: regression for importing extensions in packages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]