[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Changes by Berker Peksag : -- nosy: +berker.peksag stage: patch review -> needs patch type: -> behavior versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Changes by Ezio Melotti ezio.melo...@gmail.com: -- stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17383 ___ ___

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Nitika Agarwal added the comment: Hi, I would like to propose a patch for this issue. -- nosy: +nitika ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17383 ___

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Nitika Agarwal added the comment: Hello everyone, I have tried creating a patch for the issue, Please review the attached patch. -- keywords: +patch Added file: http://bugs.python.org/file34446/issue17383.patch ___ Python tracker

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Éric Araujo added the comment: Thanks for the patch. +Enhancing the More on Modules documentation + This should not be in the patch. -Modules can import other modules. It is customary but not required -to place all import

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Éric Araujo added the comment: I was not disagreeing that there was an ambiguity, just trying to explain why some people would understand the text in a different way that what it meant. -- stage: - needs patch ___ Python tracker

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Éric Araujo added the comment: Ah, we have it: the tutorial distinguishes between “it’s customary to put imports near the top of the file” vs. “later in the file”, and you interpret it as “it’s customary to put imports at the module top level” vs. “import in any scope e.g. functions”. These

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Jeff Knupp added the comment: Of the two different things, the first (the scope of imported names) is never covered in the documentation. As a result, the text in question seems to imply an import statement can *only* be in module scope. From the reader's perspective: If I wanted to import

[issue17383] Possibly ambiguous phrasing in tutorial/modules#more-on-modules

Piotr Kuchta added the comment: Eric, when you say 'the tutorial distinguishes between “it’s customary to put imports near the top of the file” vs. “later in the file”' the last bit is just your interpretation. The tutorial doesn't say later in the file. Anyway, 'later in the file' does not