[issue38349] Email example using imaginary library installation error.

Abhilash Raj added the comment: We could move that comment to the top near the import, I am totally fine with that. -- ___ Python tracker ___

[issue38349] Email example using imaginary library installation error.

jackotonye added the comment: I’m fine with closing the issue. Seems trivial now after reading the comments but noting that most developers take examples as running code and spend less time going over the comments and a dependency that had similar names makes it even harder to make the

[issue38349] Email example using imaginary library installation error.

Abhilash Raj added the comment: The comment should make it clear that it is an made up imaginary module. The no dependencies outside of standard library is not written, I guess? -- ___ Python tracker

[issue38349] Email example using imaginary library installation error.

Abhilash Raj added the comment: The function of this imaginary method is described below: # The magic_html_parser has to rewrite the href="cid:" attributes to # point to the filenames in partfiles. It also has to do a safety-sanitize # of the html. It could be written using

[issue38349] Email example using imaginary library installation error.

SilentGhost added the comment: One fairly naive solution would be to define a magic_html_parser directly in the example and move explanatory comment there. In order not to break the code it could return an empty string. -- ___ Python tracker

[issue38349] Email example using imaginary library installation error.

Terry J. Reedy added the comment: The rest of the overly long title was "The install shows that it only supports python 2.x but is listed under python 3.6+ docs." The lines in question are from the 2nd to last example. # An imaginary module that would make this work and be safe. from

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

jackotonye added the comment: Might be best to make it a little more obvious since most examples are considered executable code. That would require little modification. On Wed, Oct 2, 2019 at 12:20 PM SilentGhost wrote: > > SilentGhost added the comment: > > imaginary in the example is not

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

SilentGhost added the comment: imaginary in the example is not meant to refer to https://pypi.org/project/Imaginary/ it's meant to refer to a module that you could write that would do all the dirty work. Perhaps, it's not the best name to use provided there is an actual module on pypi,

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

Change by jackotonye : -- title: Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed for python 3.6+ -> Email example using imaginary library installation error. The install shows that it only supports python 2.x

[issue38349] Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed for python 3.6+

New submission from jackotonye : https://docs.python.org/3.7/library/email.examples.html -- assignee: docs@python components: Documentation messages: 353743 nosy: docs@python, jackotonye priority: normal severity: normal status: open title: Email example using imaginary library