[issue2400] from .foo import * should work

2010-08-05 Thread Jason R. Coombs
Jason R. Coombs added the comment: Is there any chance this can be back-ported to Python 2.7? -- ___ Python tracker ___ ___ Python-bug

[issue2400] from .foo import * should work

2010-08-05 Thread Jason R. Coombs
Changes by Jason R. Coombs : -- nosy: +jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue2400] from .foo import * should work

2008-03-18 Thread Martin v. Löwis
Martin v. Löwis <[EMAIL PROTECTED]> added the comment: This is now fixed in r61595. -- nosy: +loewis resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue2400] from .foo import * should work

2008-03-18 Thread Benjamin Peterson
Benjamin Peterson <[EMAIL PROTECTED]> added the comment: More verbosely: The restriction should be removed; a SyntaxError shouldn't be raised, and import should handle it correctly. -- nosy: +benjamin.peterson __ Tracker <[EMAIL PROTECTED]>

[issue2400] from .foo import * should work

2008-03-18 Thread Neal Norwitz
New submission from Neal Norwitz <[EMAIL PROTECTED]>: Explicit relative imports using from .foo import * should work. http://mail.python.org/pipermail/python-3000/2008-March/012564.html -- components: Interpreter Core messages: 63942 nosy: nnorwitz priority: critical severity: normal st