[issue44896] AttributeError in ast.unparse

Łukasz Langa added the comment: Sorry, I think we shouldn't be changing `ast.py` this way. To reiterate my review comment from the PR: I think we should just let this go and instead advertise that if you put new synthetic nodes in a tree, you have to either: - provide `lineno` and

Re: OT: AttributeError

On Wed, Sep 29, 2021 at 12:06 PM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > ... Or, even better, to be able to read off a hex dump and see E8 03 > > and instantly read it as "1,000 little-endian". > > 59535 big endian. Warningm flamebait ahead: Who thinks in little > endian? (I was raised

Re: OT: AttributeError

On 2021-09-29 at 09:21:34 +1000, Chris Angelico wrote: > ... read off a hex dump and see E8 > 03 and instantly read it as "1,000 little-endian". ITYM 000,1 little-endian. ;-) (Or possibly 000.1, depending on your locale.) -- https://mail.python.org/mailman/listinfo/python-list

Re: OT: AttributeError

On 2021-09-29 at 09:21:34 +1000, Chris Angelico wrote: > On Wed, Sep 29, 2021 at 9:10 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > > > On 2021-09-29 at 11:38:22 +1300, > > dn via Python-list wrote: > > > > > For those of us who remember/can compute in binary, octal, hex, or > > > decimal

Re: OT: AttributeError

On Wed, Sep 29, 2021 at 11:59 AM dn via Python-list wrote: > If I hold up two fingers, am I insulting you, or asking for three of > something? > A Roman soldier walked into a bar holding up two fingers. "Five beers, please" ChrisA -- https://mail.python.org/mailman/listinfo/python-list

Re: OT: AttributeError

On 29/09/2021 12.21, Chris Angelico wrote: > On Wed, Sep 29, 2021 at 9:10 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: >> >> On 2021-09-29 at 11:38:22 +1300, >> dn via Python-list wrote: >> >>> For those of us who remember/can compute in binary, octal, hex, or >>> decimal as-needed: >>> Why do

Re: OT: AttributeError

On Wed, Sep 29, 2021 at 10:06 AM Greg Ewing wrote: > > On 29/09/21 12:21 pm, Chris Angelico wrote: > > to the extent that you automatically read 65 and 0x41 as the same > > number. > > Am I too geeky for reading both of them as 'A'? > Not even slightly, and I did deliberately choose a printable

Re: OT: AttributeError

On 29/09/21 12:21 pm, Chris Angelico wrote: to the extent that you automatically read 65 and 0x41 as the same number. Am I too geeky for reading both of them as 'A'? -- Greg -- https://mail.python.org/mailman/listinfo/python-list

Re: OT: AttributeError

On Wed, Sep 29, 2021 at 9:10 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > On 2021-09-29 at 11:38:22 +1300, > dn via Python-list wrote: > > > For those of us who remember/can compute in binary, octal, hex, or > > decimal as-needed: > > Why do programmers confuse All Hallows'/Halloween for

Re: OT: AttributeError

On 2021-09-29 at 11:38:22 +1300, dn via Python-list wrote: > For those of us who remember/can compute in binary, octal, hex, or > decimal as-needed: > Why do programmers confuse All Hallows'/Halloween for Christmas Day? That one is also very old. (Yes, I know the answer. No, I will not spoil

OT: AttributeError

On 29/09/2021 10.50, Stefan Ram wrote: > (For Python programmers who have watched "Game of Thrones".) > > |>>> class girl: > |... pass > |... > |>>> girl = girl() > |>>> print( girl.name ) > |Traceback (most recent call last): &g

[issue11255] 2to3 throws AttributeError during distutils installation with -O

Irit Katriel added the comment: Python 3.2 is out of date, and distutils and 2to3 are both deprecated. -- nosy: +iritkatriel resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python tracker

[issue36550] Avoid creating AttributeError exceptions in the debugger

Irit Katriel added the comment: Reopened. -- resolution: rejected -> status: closed -> open versions: -Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___

[issue36550] Avoid creating AttributeError exceptions in the debugger

__import__('pdb').set_trace() ``` ``` % ./python t_issue36550.py --Return-- > …/t_issue36550.py(5)()->None -> __import__('pdb').set_trace() (Pdb) import sys; sys.exc_info() (, AttributeError("'Pdb' object has no attribute 'do_import'"), ) ``` The initial / better motiv

[issue36550] Avoid creating AttributeError exceptions in the debugger

Irit Katriel added the comment: Closing as the bug is not clear and the OP is not responding to requests on the PR to clarify it. Please create a new issue if you are still seeing a problem. -- nosy: +iritkatriel resolution: -> rejected stage: patch review -> resolved status: open

[issue42959] AttributeError: module 'signal' has no attribute 'SIGHUP'

Change by Irit Katriel : -- pull_requests: -26608 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42959] AttributeError: module 'signal' has no attribute 'SIGHUP'

Change by Irit Katriel : -- nosy: +iritkatriel nosy_count: 6.0 -> 7.0 pull_requests: +26608 pull_request: https://github.com/python/cpython/pull/23688 ___ Python tracker ___

[issue45064] Raising AttributeError in descriptor decorator causing searching attribute in __mro__

Raymond Hettinger added the comment: To get a better insight into what is going on, see https://docs.python.org/3/howto/descriptor.html#invocation-from-an-instance The relevant text is, "So if __getattr__() exists, it is called whenever __getattribute__() raises AttributeError (e

[issue45064] Raising AttributeError in descriptor decorator causing searching attribute in __mro__

Yurii Karabas <1998uri...@gmail.com> added the comment: Hi Mateusz, It's not a bug, it's expected behavior. __getattr__ called when the default attribute access fails with an AttributeError (either __getattribute__() raises an AttributeError because name is not an instance att

[issue45064] Raising AttributeError in descriptor decorator causing searching attribute in __mro__

New submission from Mateusz : A descriptor that is raising AttributeError in __get__() causes that the Python's interpreter continues searching for attributes in __mro__ calling __getattr__() function in inherited classes. Let's take a look for example script with this bug. class A1

[issue44896] AttributeError in ast.unparse

Change by Łukasz Langa : -- versions: +Python 3.10, Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44896] AttributeError in ast.unparse

Change by Batuhan Taskaya : -- keywords: +patch pull_requests: +26245 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27770 ___ Python tracker ___

[issue44896] AttributeError in ast.unparse

Batuhan Taskaya added the comment: I don't think this is really an issue considering some other functionalities that consumes AST code (e.g `compile`) will expect it to be annotated with location metadata. This is why the `ast` module already comes bundled with a utility function called

[issue44896] AttributeError in ast.unparse

Change by Terry J. Reedy : -- title: Issue with unparse in ast module -> AttributeError in ast.unparse ___ Python tracker <https://bugs.python.org/issu

[issue42892] AttributeError in email.message.get_body()

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior ___ Python tracker ___

[issue42892] AttributeError in email.message.get_body()

Łukasz Langa added the comment: New changeset 0f42b726c87f72d522893f927b4cb592b8875641 by Miss Islington (bot) in branch '3.9': bpo-42892: fix email multipart attribute error (GH-26903) (GH-27493) https://github.com/python/cpython/commit/0f42b726c87f72d522893f927b4cb592b8875641 --

[issue42892] AttributeError in email.message.get_body()

Łukasz Langa added the comment: New changeset 6f950023c6a2168b229363d75f59a24ecdd66d19 by Miss Islington (bot) in branch '3.10': bpo-42892: fix email multipart attribute error (GH-26903) (GH-27492) https://github.com/python/cpython/commit/6f950023c6a2168b229363d75f59a24ecdd66d19 --

[issue42892] AttributeError in email.message.get_body()

Change by miss-islington : -- pull_requests: +26009 pull_request: https://github.com/python/cpython/pull/27493 ___ Python tracker ___

[issue42892] AttributeError in email.message.get_body()

Łukasz Langa added the comment: New changeset e3f877c32d7cccb734f45310f26beeec793364ce by andrei kulakov in branch 'main': bpo-42892: fix email multipart attribute error (GH-26903) https://github.com/python/cpython/commit/e3f877c32d7cccb734f45310f26beeec793364ce -- nosy:

[issue42892] AttributeError in email.message.get_body()

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +26008 pull_request: https://github.com/python/cpython/pull/27492 ___ Python tracker

[issue44717] Improve AttributeError on circular imports of submodules

Change by Filipe Laíns : -- pull_requests: +25886 pull_request: https://github.com/python/cpython/pull/27344 ___ Python tracker ___

[issue44717] Improve AttributeError on circular imports of submodules

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44717] Improve AttributeError on circular imports of submodules

Pablo Galindo Salgado added the comment: New changeset 0a8ae8a50a0fea3d39ec49b220a5c7a5b70e36f8 by Filipe Laíns in branch 'main': bpo-44717: improve AttributeError on circular imports of submodules (GH-27338) https://github.com/python/cpython/commit/0a8ae8a50a0fea3d39ec49b220a5c7a5b70e36f8

[issue44717] Improve AttributeError on circular imports of submodules

Change by Filipe Laíns : -- pull_requests: +25881 pull_request: https://github.com/python/cpython/pull/27338 ___ Python tracker ___

[issue44717] Improve AttributeError on circular imports of submodules

Pablo Galindo Salgado added the comment: New changeset 3eae8f20d7b6f88d3618b0afc94893165a914022 by Pablo Galindo Salgado in branch 'main': Revert "bpo-44717: improve AttributeError on circular imports of submodules (GH-27299)" (GH-27331) https://github.com/python/cpyt

[issue44717] Improve AttributeError on circular imports of submodules

Change by Pablo Galindo Salgado : -- pull_requests: +25874 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/27331 ___ Python tracker ___

[issue44717] Improve AttributeError on circular imports of submodules

Pablo Galindo Salgado added the comment: There is a buildbot failure after merging this PR: https://buildbot.python.org/all/#/builders/464/builds/574 If is not fixed in 24 we will need to revert per our buildbot policy -- resolution: fixed -> status: closed -> open

[issue44717] Improve AttributeError on circular imports of submodules

Łukasz Langa added the comment: Thanks a lot for your report and patch, Filipe! ✨  ✨ -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue44717] Improve AttributeError on circular imports of submodules

Łukasz Langa added the comment: New changeset 8072a1181dd64135f700b44372fbf7bf91e68072 by Filipe Laíns in branch 'main': bpo-44717: improve AttributeError on circular imports of submodules (GH-27299) https://github.com/python/cpython/commit/8072a1181dd64135f700b44372fbf7bf91e68072

[issue44717] Improve AttributeError on circular imports of submodules

Change by Filipe Laíns : -- keywords: +patch pull_requests: +25842 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27299 ___ Python tracker ___

[issue44717] Improve AttributeError on circular imports of submodules

"help", "copyright", "credits" or "license" for more information. >>> import a.b Traceback (most recent call last): File "", line 1, in File "/home/anubis/test/a/b/__init__.py", line 1, in import a.b.c File "/home

[issue44655] Confusing message with AttributeError when attribute name matches suggestion

Pablo Galindo Salgado added the comment: New changeset efda9054b9fc91e69ecb34eae84fdd2ca8e6feef by Miss Islington (bot) in branch '3.10': bpo-44655: Include the name of the type in unset __slots__ attribute errors (GH-27199) (GH-27201)

[issue44655] Confusing message with AttributeError when attribute name matches suggestion

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44655] Confusing message with AttributeError when attribute name matches suggestion

Change by miss-islington : -- pull_requests: +25735 pull_request: https://github.com/python/cpython/pull/27201 ___ Python tracker ___

[issue44655] Confusing message with AttributeError when attribute name matches suggestion

Pablo Galindo Salgado added the comment: New changeset f783428a2313a729ca8b539c5a86ff114b9ff375 by Pablo Galindo Salgado in branch 'main': bpo-44655: Include the name of the type in unset __slots__ attribute errors (GH-27199)

[issue44655] Confusing message with AttributeError when attribute name matches suggestion

Change by Pablo Galindo Salgado : -- pull_requests: +25734 pull_request: https://github.com/python/cpython/pull/27199 ___ Python tracker ___

[issue44655] Confusing message with AttributeError when attribute name matches suggestion

Change by Eric V. Smith : -- title: Confusing message with AttributreError when attribute name matches suggestion -> Confusing message with AttributeError when attribute name matches suggestion ___ Python tracker <https://bugs.pyth

[issue44576] AttributeError: incorrect line identified in Python 3.10

Change by Mark Shannon : -- priority: release blocker -> resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue44576] AttributeError: incorrect line identified in Python 3.10

Pablo Galindo Salgado added the comment: > I'm inclined to leave it as is I am fine with that, if you think this is not a bug, close the issue and remove the release blocker :) -- ___ Python tracker

[issue44576] AttributeError: incorrect line identified in Python 3.10

Andre Roberge added the comment: While I filed the original report, I am in agreement that accurate information for debugging tools is definitely more important than the quick summary shown in the traceback, and that the change likely represents an improvement in situations more realistic

[issue44576] AttributeError: incorrect line identified in Python 3.10

Mark Shannon added the comment: This is a tricky one. Which is the "correct" line appears to be subjective. I'm inclined to leave it as is, as the tracing sequence seems better in the case of method chaining. See https://github.com/python/cpython/blob/main/Lib/test/test_compile.py#L890

[issue44576] AttributeError: incorrect line identified in Python 3.10

Pablo Galindo Salgado added the comment: Mark, take a look as soon as possible as beta4 is this week -- nosy: +pablogsal priority: normal -> release blocker ___ Python tracker

[issue44576] AttributeError: incorrect line identified in Python 3.10

Alex Hall added the comment: (meant to say "so I'm pulling in @Mark.Shannon) -- ___ Python tracker ___ ___ Python-bugs-list

[issue44576] AttributeError: incorrect line identified in Python 3.10

Alex Hall added the comment: I believe this is the outcome of https://bugs.python.org/issue39316 which I filed, so I'm pulling in . Naturally I think the new behaviour is not a bug but a feature. I think it's more important for the traceback to show the attribute access (`two`) than the

[issue44576] AttributeError: incorrect line identified in Python 3.10

ple.py", line 3, in a = [one AttributeError: 'int' object has no attribute 'two' The line shown correctly includes the 'int' object. I have verified that this is the case for Python 3.6 to 3.9 inclusively. However, with Python version 3.10.0b3, the following traceback is generated: Tr

[issue39100] email.policy.SMTP throws AttributeError on invalid header

Anton Khirnov added the comment: Quoting Andrei Kulakov (2021-07-03 16:03:34) > Anton: thanks for the report! In the message you say you are not sure > of the solution, and because of that not sending a patch, but then you > created the PR; - please clarify. I didn't send a patch when

[issue39100] email.policy.SMTP throws AttributeError on invalid header

Anton Khirnov added the comment: Quoting R. David Murray (2021-07-06 18:59:56) > How are you encountering this error? The following program runs without > exception for me on master: > > from email import message_from_binary_file > from email.policy import SMTP > > msg =

[issue39100] email.policy.SMTP throws AttributeError on invalid header

Andrei Kulakov added the comment: I should have been more exact - I've used python3.7.7 . -- ___ Python tracker ___ ___

[issue39100] email.policy.SMTP throws AttributeError on invalid header

Andrei Kulakov added the comment: Running R.David's test script on python3.7, it also works, there's no exception. -- ___ Python tracker ___

[issue39100] email.policy.SMTP throws AttributeError on invalid header

R. David Murray added the comment: How are you encountering this error? The following program runs without exception for me on master: from email import message_from_binary_file from email.policy import SMTP msg = message_from_binary_file(open('mail.eml', 'rb'), policy=SMTP) print(msg)

[issue39100] email.policy.SMTP throws AttributeError on invalid header

Andrei Kulakov added the comment: Anton: thanks for the report! In the message you say you are not sure of the solution, and because of that not sending a patch, but then you created the PR; - please clarify. -- nosy: +andrei.avk ___ Python

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Serhiy Storchaka added the comment: New changeset 20a88004bae8ead66a205a125e1fe979376fc3ea by Serhiy Storchaka in branch 'main': bpo-12022: Change error type for bad objects in "with" and "async with" (GH-26809)

[issue42892] AttributeError in email.message.get_body()

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

E. Paine added the comment: > Can you change labels on your own PRs? Sadly not (hence why I need to ask for e.g. skip news) -- ___ Python tracker ___

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Serhiy Storchaka added the comment: There were some issues with the backporting bot. Seems they were temporary. Thank you for your contribution E. Paine. For this issue and others. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

miss-islington added the comment: New changeset e1f3bd2bb50a76ba15a2f8d561e2c9968ae3a1b2 by Miss Islington (bot) in branch '3.10': bpo-44404: tkinter `after` support callable classes (GH-26812) https://github.com/python/cpython/commit/e1f3bd2bb50a76ba15a2f8d561e2c9968ae3a1b2 --

[issue36991] zipfile: AttributeError on extract

Change by Gregory P. Smith : -- stage: patch review -> resolved status: pending -> closed ___ Python tracker ___ ___

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Change by Terry J. Reedy : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Terry J. Reedy added the comment: When the backport is done or Serhiy changes his mind. Can you change labels on your own PRs? -- nosy: -miss-islington stage: patch review -> ___ Python tracker

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +25494 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26921 ___ Python tracker

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

E. Paine added the comment: Can this issue be closed? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42892] AttributeError in email.message.get_body()

Andrei Kulakov added the comment: Put up the PR here: https://github.com/python/cpython/pull/26903 -- ___ Python tracker ___ ___

[issue42892] AttributeError in email.message.get_body()

Change by Andrei Kulakov : -- pull_requests: +25479 pull_request: https://github.com/python/cpython/pull/26903 ___ Python tracker ___

[issue42892] AttributeError in email.message.get_body()

Andrei Kulakov added the comment: I'll try to fix the unit test today. -- nosy: +andrei.avk ___ Python tracker ___ ___

[issue36991] zipfile: AttributeError on extract

Irit Katriel added the comment: This seems resolved, can we close? -- nosy: +iritkatriel resolution: -> fixed status: open -> pending ___ Python tracker ___

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Terry J. Reedy added the comment: I was thinking the same. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Serhiy Storchaka added the comment: It is on borderline between new feature and bugfix (depends on your interpretation of the documentation), so I decided to backport it to not yet released 3.10, but not to 3.9 which has been already used for a year. -- stage: patch review -> type:

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Serhiy Storchaka added the comment: New changeset e9c8f784fa13ea3a51df3b72a498a3896ec9e768 by E-Paine in branch 'main': bpo-44404: tkinter `after` support callable classes (GH-26812) https://github.com/python/cpython/commit/e9c8f784fa13ea3a51df3b72a498a3896ec9e768 --

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Change by E. Paine : -- keywords: +patch pull_requests: +25394 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26812 ___ Python tracker ___

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Serhiy Storchaka added the comment: PR 26809 makes "with" and "async with" raising TypeError instead of AttributeError for wrong types. -- ___ Python tracker <https://bug

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Change by Serhiy Storchaka : -- nosy: +gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +25391 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26809 ___ Python tracker

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Change by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Irit Katriel added the comment: I've reproduced this on 3.11 (though the AttributeError is now on __enter__ and not __exit__ as was the case in msg135484): >>> import transaction >>> with transaction: pass ... Traceback (most recent call last): File ""

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

Terry J. Reedy added the comment: The docstring for .after says the 2nd argument must be a 'function'. Whether this issue is a bugfix or enhancement request depends whether one interprets 'function' as 'callable' or something narrower that only includes objects that necessarily have

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

E. Paine added the comment: Reproducible in Python 3.9. The issue occurs because functools.partial is a class, not function. I believe the fix is simply something like: try: callit.__name__ = func.__name__ except AttributeError: callit.__name__ = type(func).__name__ This will use

[issue44404] tkinter's after() AttributeError with functools.partial (no attribute __name__)

python3.7/tkinter/__init__.py", line 755, in after callit.__name__ = func.__name__ AttributeError: 'functools.partial' object has no attribute '__name__' ``` -- components: Tkinter messages: 395712 nosy: phil.tgd priority: normal severity: normal status: open title: tkinter's after() A

[issue44266] AttributeError: module 'sys' has no attribute 'original_stdout'

Terry J. Reedy added the comment: If you intend to import the stdlib sys and succeed, the original stdout is called '__stdout__'. See https://docs.python.org/3/library/sys.html#sys.__stdin__, including the note that it may be None on Windows. Also peruse that doc to see what attributes

[issue44266] AttributeError: module 'sys' has no attribute 'original_stdout'

Steven D'Aprano added the comment: Correct, sys has no attribute 'original_stdout'. Do you have a file called `sys.py`? Rename it. -- nosy: +steven.daprano ___ Python tracker

[issue44266] AttributeError: module 'sys' has no attribute 'original_stdout'

New submission from Chinmay Malvania : I imported sys but when I use it, it says: AttributeError: module 'sys' has no attribute 'original_stdout' -- messages: 394746 nosy: chinmay.malvania priority: normal severity: normal status: open title: AttributeError: module 'sys' has

[issue41830] "NameError: name 'AttributeError' is not defined"

Irit Katriel added the comment: Sanka, please create a new issue if you can provide more info about the problem. -- stage: -> resolved status: pending -> closed ___ Python tracker

[issue42892] AttributeError in email.message.get_body()

R. David Murray added the comment: Actually, I'm wrong. The body of a part can be a string, and that's what's going to happen with a malformed body of something claiming to be a multipart. The problem is that there is code that doesn't guard against this possibility. The following patch

[issue42892] AttributeError in email.message.get_body()

R. David Murray added the comment: Yes, that's the real question. That's what needs to be fixed, otherwise we'll just keep finding new bugs. For example, try calling iter_parts() on that message. It isn't pretty :) -- ___ Python tracker

[issue42892] AttributeError in email.message.get_body()

Irit Katriel added the comment: Can you see how it happened that part is a str? -- ___ Python tracker ___ ___ Python-bugs-list

[issue41830] "NameError: name 'AttributeError' is not defined"

Irit Katriel added the comment: The link to the logs is not working now, and without more info there isn't much we can do. Sanka, are you able to reproduce this on a newer python version and tell us how? -- nosy: +iritkatriel resolution: -> rejected status: open -> pending

[issue44026] IDLE: print "Did you mean?" for AttributeError and NameError

Change by Terry J. Reedy : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44026] IDLE: print "Did you mean?" for AttributeError and NameError

call last): File "", line 2, in except NameError: f"{complex.reel(1+1j)} errors occurred!" AttributeError: type object 'complex' has no attribute 'reel'. Did you mean: 'real'? And thank you Pablo for making exception messages more helpful. -- stage: patch review -> __

[issue44026] IDLE: print "Did you mean?" for AttributeError and NameError

Terry J. Reedy added the comment: New changeset 5a5237c6d08ed97458b0903d6836624168df0b51 by Miss Islington (bot) in branch '3.10': bpo-44026: Idle - display interpreter's 'did you mean' hints (GH-25912) https://github.com/python/cpython/commit/5a5237c6d08ed97458b0903d6836624168df0b51

[issue44026] IDLE: print "Did you mean?" for AttributeError and NameError

Change by Terry J. Reedy : -- pull_requests: +24631 pull_request: https://github.com/python/cpython/pull/25975 ___ Python tracker ___

<    1   2   3   4   5   6   7   8   9   10   >