[issue11614] import __hello__ is broken in Python 3

Solomon Ucko added the comment: > It changes the semantics of Python. When would the return value actually matter? Would it affect the value of the variable `__hello__`? -- ___ Python tracker _

[issue11614] import __hello__ is broken in Python 3

Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue11614] import __hello__ is broken in Python 3

STINNER Victor added the comment: > The byte code could be further optimized (because this is such a > speed-critical module! :)): (...) You propose to replace 8 CALL_FUNCTION1 10 POP_TOP 12 LOAD_CONST 2 (None) 14

[issue11614] import __hello__ is broken in Python 3

Solomon Ucko added the comment: The byte code could be further optimized (because this is such a speed-critical module! :)): 1 0 LOAD_CONST 2 (True) 3 STORE_NAME 1 (initialized) 2 6 LOAD_NAME2 (print)

[issue11614] import __hello__ is broken in Python 3

Roundup Robot added the comment: New changeset 47bc3509f76b by Victor Stinner in branch '2.7': Issue #11614: Fix test_linecache, cjkencodings_test.py doesn't exist anymore http://hg.python.org/cpython/rev/47bc3509f76b -- ___ Python tracker

[issue11614] import __hello__ is broken in Python 3

STINNER Victor added the comment: > New changeset 9a4d4506680a by Victor Stinner in branch '3.1': > Issue #11614: Fix test_linecache, cjkencodings_test.py doesn't exist anymore Oh, these commits are related to #12057, not this one. -- ___ Python tra

[issue11614] import __hello__ is broken in Python 3

Roundup Robot added the comment: New changeset 9a4d4506680a by Victor Stinner in branch '3.1': Issue #11614: Fix test_linecache, cjkencodings_test.py doesn't exist anymore http://hg.python.org/cpython/rev/9a4d4506680a New changeset 43cbfacae463 by Victor Stinner in branch '3.2': (Merge 3.1) Iss

[issue11614] import __hello__ is broken in Python 3

Roundup Robot added the comment: New changeset 9e1d7cd15d2e by Victor Stinner in branch '3.1': Issue #11614: Fix importlib tests for the new __hello__ module http://hg.python.org/cpython/rev/9e1d7cd15d2e New changeset 6119f6cc9b2d by Victor Stinner in branch '3.2': (Merge 3.1) Issue #11614: Fix

[issue11614] import __hello__ is broken in Python 3

STINNER Victor added the comment: Thanks Andreas for your fix! Python 3 is now better than Python 2: it prints "Hello World!" instead of "Hello World...". -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue11614] import __hello__ is broken in Python 3

Roundup Robot added the comment: New changeset 44fd95cead7b by Victor Stinner in branch '3.1': Issue #11614: import __hello__ prints "Hello World!". Patch written by Andreas http://hg.python.org/cpython/rev/44fd95cead7b New changeset 2c5736e8a221 by Victor Stinner in branch '3.2': (Merge 3.1) I

[issue11614] import __hello__ is broken in Python 3

Changes by Georg Brandl : -- priority: release blocker -> deferred blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue11614] import __hello__ is broken in Python 3

Changes by Andreas Stührk : Added file: http://bugs.python.org/file21988/issue11614_!.patch ___ Python tracker ___ ___ Python-bugs-list mailin

[issue11614] import __hello__ is broken in Python 3

STINNER Victor added the comment: +print("Hello world...") I would prefer a more positive "Hello World!", but thanks for the patch. -- ___ Python tracker ___ __

[issue11614] import __hello__ is broken in Python 3

Andreas Stührk added the comment: A patch against 3.1. The new bytecode is now: 1 0 LOAD_CONST 2 (True) 3 STORE_NAME 1 (initialized) 2 6 LOAD_NAME2 (print) 9 LOAD_CONST 0 ('Hello wo

[issue11614] import __hello__ is broken in Python 3

STINNER Victor added the comment: > Why is this still open Because import __hello__ doesn't print hello. > and more importantly, why is it a release blocker? Because it is a very important issue! -- ___ Python tracker

[issue11614] import __hello__ is broken in Python 3

Georg Brandl added the comment: Why is this still open, and more importantly, why is it a release blocker? -- ___ Python tracker ___

[issue11614] import __hello__ is broken in Python 3

Éric Araujo added the comment: I can see the message (“Hello world...”) in 2.4 to 2.7, but actually not in 3.x. -- ___ Python tracker ___ ___

[issue11614] import __hello__ is broken in Python 3

Andreas Stührk added the comment: On Fri, Mar 25, 2011 at 5:52 PM, Éric Araujo wrote: > Okay, it doesn’t work with -m __hello__, but using -c "import __hello__" I > can see the message in all versions. Can you elaborate on that? I.e. the versions and the actual message. The current bytecode o

[issue11614] import __hello__ is broken in Python 3

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue11614] import __hello__ is broken in Python 3

Éric Araujo added the comment: Okay, it doesn’t work with -m __hello__, but using -c "import __hello__" I can see the message in all versions. -- ___ Python tracker ___ ___

[issue11614] import __hello__ is broken in Python 3

Éric Araujo added the comment: What’s import __hello__? I don’t have it in any version from 2.4 to 3.2. -- nosy: +eric.araujo ___ Python tracker ___ ___

[issue11614] import __hello__ is broken in Python 3

Andreas Stührk added the comment: That was changed in [a2213060d9dd], see issue #1414. -- nosy: +Trundle ___ Python tracker ___ ___ P

[issue11614] import __hello__ is broken in Python 3

New submission from STINNER Victor : import __hello__ doesn't print any message!!! -- messages: 131499 nosy: benjamin.peterson, georg.brandl, haypo priority: release blocker severity: normal status: open title: import __hello__ is broken in Python 3 versions: Python 3.1, Python 3.2, Pyth