[issue32451] python -m venv activation issue when using cygwin on windows

R. David Murray added the comment: cygwin in not currently fully supported (there are people working on it, though). Can you determine if this is a bug in cygwin's bash support, or something else? It certainly works with bash shell on unix. I would presume that from cygwin one would

[issue32452] Brackets and Parentheses used in an ambiguous way

R. David Murray added the comment: "round brackets" would require just as much thought (if not more...it's not a thing at all in American typographical language) for an American to understand as the unadorned bracket does for the rest of you, so the best compromise is "pa

[issue32448] subscriptable

R. David Murray added the comment: Well, in that case having 'organizer' in the error message wouldn't help you untangle your code ;) -- ___ Python tracker <https://bugs.pyt

[issue32462] mimetypes.guess_type() returns incorrectly formatted type

R. David Murray added the comment: You can get the same "bad" behavior on a posix system by having a mimetypes file with an incorrect entry in it. That would be a system misconfiguration, as is your Windows registry case, and is outside of Python's control. I suppose w

[issue32474] argparse nargs should support string wrapped integers too

R. David Murray added the comment: Why? What's the motivation for supporting this? There's no reason that I can think of, so I'm curious what your use case is. -- nosy: +r.david.murray ___ Python tracker <https://bugs.pyt

[issue32452] Brackets and Parentheses used in an ambiguous way

R. David Murray added the comment: New changeset f190eb59e60e2ae7a7cbd396458389a7a076e0d3 by R. David Murray (Emily Morehouse) in branch 'master': bpo-32452: clarify term 'brackets' in generator tutorial (#5079) https://github.com/python/cpython/commit/f190eb59e60e2ae7a7cb

[issue32474] argparse nargs should support string wrapped integers too

R. David Murray added the comment: Agreed. I don't think there is sufficient motivation for doing this, and there are downsides as Eric has pointed out. Rejecting. -- resolution: -> rejected stage: patch review -> resolved status: ope

[issue32452] Brackets and Parentheses used in an ambiguous way

R. David Murray added the comment: New changeset f24c1857a8a1ba3efb3f957d43371bc9499e3c86 by R. David Murray (Miss Islington (bot)) in branch '3.6': bpo-32452: clarify term 'brackets' in generator tutorial (GH-5079) (#5081) https://github.com/p

[issue32452] Brackets and Parentheses used in an ambiguous way

R. David Murray added the comment: It looks like the docs job hung on the 2.7 backport, but I don't see how to restart it. -- ___ Python tracker <https://bugs.python.org/is

[issue32452] Brackets and Parentheses used in an ambiguous way

R. David Murray added the comment: New changeset 0e0d1017a4c8ad6f77ee42d7b640463058037f62 by R. David Murray (Miss Islington (bot)) in branch '2.7': bpo-32452: clarify term 'brackets' in generator tutorial (GH-5079) (#5082) https://github.com/p

[issue32452] Brackets and Parentheses used in an ambiguous way

R. David Murray added the comment: Thanks, Mariatta. I did click on the details link, so either the restart link isn't obvious or I don't have the correct permissions to do a restart :) And thanks Emily for doing the PR. -- resolution: -> fixed stage: patch revie

[issue32487] assertRaises should return the "captured" exception

R. David Murray added the comment: This has been proposed and rejected before, for example in issue 28135. If you want to pursue it you'll need to start a thread on python-ideas. -- nosy: +r.david.murray resolution: -> duplicate stage: needs patch -> resolved status: ope

[issue32488] Fatal error using pydoc

Change by R. David Murray : -- components: +macOS nosy: +ned.deily, ronaldoussoren ___ Python tracker <https://bugs.python.org/issue32488> ___ ___ Python-bug

[issue32491] base64.decode: linebreaks are not ignored

R. David Murray added the comment: This reduces to the following: >>> from binascii import a2b_base64 as f >>> f(b'MTIzND\nU2Nzg5\n') b'123456789' >>> f(b'MTIzND\n') Traceback (most recent call last): File "", line 1, in b

[issue17972] inspect module docs omits many functions

R. David Murray added the comment: I think adding an __all__ in 3.7 would be reasonable. You are right that we can't simply rename them for backward compatibility reasons. We could rename them, and leave a stub function (that calls the renamed function) but issues a deprecation wa

[issue17972] inspect module docs omits many functions

R. David Murray added the comment: Just warnings, no docs. We've done this before for other helper functions, but it is always a judgement call whether it is worth the churn. I defer to those people who have actually done work on the module for the answer to that que

[issue32498] urllib.parse.unquote raises incorrect errormessage when string parameter is bytes

R. David Murray added the comment: If you read the traceback the message is "correct" for some definition of correct: the right hand side controls the type of the expression, so it is objecting to trying to look for the string '%' in a bytes object. There are probabl

[issue32501] Documentation for dir([object])

R. David Murray added the comment: This is a general property of dunder methods in python3, and I think we have chosen not to change the wording when this has come up in other contexts. I'm not sure, though. -- nosy: +r.david.murray ___ P

[issue32501] Documentation for dir([object])

R. David Murray added the comment: I'm not sure, but the discussion I remember was that it would require changes to an awful lot of places in the docs that would make the docs harder to read. It is very seldom in normal Python coding that an object has a method that it does *not* get

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

R. David Murray added the comment: What happens if you print a placeholder line first, before your test output? I'm not sure it will work, I seem to remember something about an ellipses starting a line just not being supported, but it was a long time ago... So, that doesn't work

[issue32509] doctest syntax ambiguity between continuation line and ellipsis

R. David Murray added the comment: Ah, I see my answer crossed with your post :) -- ___ Python tracker <https://bugs.python.org/issue32509> ___ ___ Python-bug

[issue32498] urllib.parse.unquote raises incorrect errormessage when string parameter is bytes

R. David Murray added the comment: We generally don't do type checking (see discussions of "duck typing"). We generally do just let the implementation detail bubble up. I don't think the encoding suggestion works, since we can't know what encoding the byte string i

[issue32498] urllib.parse.unquote raises incorrect errormessage when string parameter is bytes

R. David Murray added the comment: I think Nick was the last one who touched the byte/string issues in urllib, so I've nosied him. We'll see what he thinks (but this tracker accepts enhancement proposals as long as they are smallish ones). -- nosy:

[issue32518] HTTPServer can't deal with persistent connection properly

R. David Murray added the comment: Yes, I would say it is. Note that this isn't going to get "fixed" in 2.7, because 2.7 doesn't get new features, and the proposed change to the CLI is a new feature. As noted in that issue discussion we aren't going to change the

[issue32518] HTTPServer can't deal with persistent connection properly

R. David Murray added the comment: In particular, if we don't already have an example of using the threading mixin we should, so a doc RFE to add that would be nice. -- ___ Python tracker <https://bugs.python.org/is

[issue32518] HTTPServer can't deal with persistent connection properly

R. David Murray added the comment: Well, it does support a persistent connection, but that connection lasts until it is shut down from the other side. Documentation improvement suggestions are welcome. -- ___ Python tracker <ht

[issue33547] Relative imports do not replace local variables

R. David Murray added the comment: It's importing 'a' from '.', which I guess in this context means from the current namespace (__main__), and a is 7. You'll note that 'b' did get repointed, but it got repointed to what 'a' points to, in

[issue33547] Relative imports do not replace local variables

R. David Murray added the comment: It's the same answer. __init__ *is* the package namespace, so you are setting the value of 'func' in the package (.) namespace, and what import is doing is correct. I know this is confusing. I banged my head against it while debugging

[issue33547] Relative imports do not replace local variables

R. David Murray added the comment: Yes, you are substantially correct. A subtlety that may enhance your understanding (if it doesn't instead totally confuse you :) is that __init__ is simply the most straightforward way to affect the module namespace. You would see the same phenomen

[issue33581] Document "optional components that are commonly included in Python distributions."

R. David Murray added the comment: As I understand it, we don't control or know what that list is, it depends on each distribution's policies. -- nosy: +r.david.murray ___ Python tracker <https://bugs.python.o

[issue25457] json dump fails for mixed-type keys when sort_keys is specified

R. David Murray added the comment: I'm fairly certain (though not 100%, obviously :) that coercing first and then sorting would be accepted if someone wants to create a PR for this. -- nosy: +r.david.murray versions: +Python 3.8 ___ Python tr

[issue25457] json dump fails for mixed-type keys when sort_keys is specified

R. David Murray added the comment: json keys *are* strings, so the fact that we support other object types as keys and coerce them to strings is an "extra feature" of python, and is actually a somewhat questionable feature. The reproducible use case is solved by the fact that dic

[issue33590] sched.enter priority has no impact on execution

R. David Murray added the comment: I think Ronald is correct. The priority argument for enter would apply if you called enter twice with two different delays, but they happen to end up pointing to the same moment in time from the scheduler's point of view. How would the computer know

[issue33633] smtplib msg['To] = appends instead of assigning

R. David Murray added the comment: smtplib doesn't define any behavior for messages. I presume you are talking about the email library? Vis the print behavior, dict-style lookup is defined to return the first matching header. If you want to see all of them, you can use get_all.

[issue33636] Unexpected behavior with * and arrays

R. David Murray added the comment: I wrote up a response before Mark closed the issue, so despite his excellent no discussion suggestion I'm going to post it for the edification of anyone reading the issue later rather than waste the work :) Nathan: this is *long* established behavi

[issue33647] Make string.replace accept a dict instead of two arguments

R. David Murray added the comment: That is not kwargs, that's a passing a dict. Which is what you would want, since the strings you want to replace might not be valid identifiers, and so couldn't be passed as keyword arguments. I think I'm -0.5 on this. I don't think

[issue33647] Make string.replace accept a dict instead of two arguments

Change by R. David Murray : -- versions: -Python 3.6, Python 3.7 ___ Python tracker <https://bugs.python.org/issue33647> ___ ___ Python-bugs-list mailin

[issue33667] Mock calls on mutable objects

Change by R. David Murray : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Python unittest.mock.mock_calls stores references to arguments instead of their values ___ Python tracker <https://

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

R. David Murray added the comment: If a sequence as a value means repeated instances of a key with each value from the list, then logically an empty list means no instances of the key, as documented. Blank values aren't really part of the standard (such as it is): the absence

[issue22021] shutil.make_archive() root_dir do not work

R. David Murray added the comment: Sounds reasonable to me. -- ___ Python tracker <https://bugs.python.org/issue22021> ___ ___ Python-bugs-list mailin

[issue29326] Blank lines in ._pth file are not ignored

R. David Murray added the comment: Vladimir, please open a new issue for this feature request. This issue is closed. -- nosy: +r.david.murray ___ Python tracker <https://bugs.python.org/issue29

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

R. David Murray added the comment: It would be odd to do that, since blank values are kept by default. -- ___ Python tracker <https://bugs.python.org/issue33

[issue33690] urlib.parse.urlencode with empty list and doseq=True drops the parameter

Change by R. David Murray : -- resolution: -> not a bug ___ Python tracker <https://bugs.python.org/issue33690> ___ ___ Python-bugs-list mailing list Un

[issue33721] os.path.exists() ought to return False if pathname contains NUL

R. David Murray added the comment: I seem to recall that this ValueError behavior was discussed at some length and it is the desired behavior. (At some previous point I think everything after the NUL was ignored.) I'm not really sure why it needs to be documented either, NULs are in

[issue24085] large memory overhead when pyc is recompiled

R. David Murray added the comment: That's presumably due to the compile-time constant-expression optimization. Have you tried bytes(0x100)? I don't think that gets treated as a constant by the optimizer (but I could be wrong since a bunch of things ahve been added to

[issue33749] pdb.Pdb constructor stdout override required to disable use_rawinput

R. David Murray added the comment: This is a duplicate of 2571 and 10396. As I commented in 10396, if you want to work on an enhancement request (for cmd) that improves the situation, it will be welcome; but as you observed what to do isn't immediately obvious, so discussion b

[issue33749] pdb.Pdb constructor stdout override required to disable use_rawinput

Change by R. David Murray : -- superseder: -> can cmd.py's API/docs for the use of an alternate stdin be improved? ___ Python tracker <https://bugs.python.org

[issue33527] Invalid child function scope

Change by R. David Murray : -- resolution: -> not a bug stage: test needed -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33770] base64 throws 'incorrect padding' exception even though the string length is a multiple of 4

R. David Murray added the comment: I always assumed that any string composed of valid base64 characters could be decoded to *something* if you added some padding characters, but apparently that was an invalid assumption. I agree that the message is incorrect for this case. -- nosy

[issue33770] base64 throws 'incorrect padding' exception when the issue is NOT with the padding

R. David Murray added the comment: I agree, but that would be a separate enhancement PR. The email library would use that capability if it existed...currently it adds padding in a loop trying to do the decode if it gets the invalid padding message. Which of course is going to fail for

[issue33774] Document that @lru_cache caches based on exactly how the function arguments are specified

R. David Murray added the comment: Agreed that this should be documented. -- nosy: +r.david.murray, rhettinger stage: -> needs patch title: Improve doc of @lru_cache to avoid misuse and confusion -> Document that @lru_cache caches based on exactly how the function argumen

[issue33687] uu.py calls os.path.chmod which doesn't exist

R. David Murray added the comment: The email module uses it, so I would object to its being removed. It may not be used often (probably only when working with old email archives), but there's no good reason I can see to break something that currently works. -- nosy: +r.david.m

[issue22454] Adding the opposite function of shlex.split()

R. David Murray added the comment: I like it, myself, though there is some danger in promoting the idea that this is a "safe" operation. It theoretically should be, but it increases the attack surface slightly if you actually use it (that is, using shell=False is always safer, b

[issue33806] Cannot re-open an existing telnet session

R. David Murray added the comment: telnetlib provides a low level interface to the telnet protocol. The dialog you mention appears to be transmitted on the telnet connection, so it is unlikely there is any bug or missing feature in telnetlib that would affect your problem. The sentence in

[issue33806] Cannot re-open an existing telnet session

Change by R. David Murray : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33806] Cannot re-open an existing telnet session

R. David Murray added the comment: To clarify: don't call open again *on that telnetlib.Telnet object*. You can certainly have more than one open connection using different telnetlib.Telnet instances, though it might be a bit challenging to manage

[issue28557] error message for bad raw readinto

Change by R. David Murray : -- nosy: +benjamin.peterson, stutzbach ___ Python tracker <https://bugs.python.org/issue28557> ___ ___ Python-bugs-list mailin

[issue33770] base64 throws 'incorrect padding' exception when the issue is NOT with the padding

R. David Murray added the comment: I think that would move it even more into the realm of a bugfix, then, since code that cared about specific binascii exceptions could be looking for that one already. -- ___ Python tracker <ht

[issue33741] UnicodeEncodeError onsmtplib.login(MAIL_USER, MAIL_PASSWORD)

R. David Murray added the comment: Duplicate of #29750. TLDR: smtplib needs to be fixed to handle binary passwords, and probably to use utf-8 as the default encoding for unicode passwords. -- nosy: +r.david.murray resolution: -> duplicate stage: -> resolved status: open -&g

[issue29750] smtplib doesn't handle unicode passwords

Change by R. David Murray : -- nosy: +JustAnother1, giampaolo.rodola, taleinat ___ Python tracker <https://bugs.python.org/issue29750> ___ ___ Python-bugs-list m

[issue29750] smtplib doesn't handle unicode passwords

R. David Murray added the comment: Note: it is definitely the case, regardless of what the RFC says, that binary passwords need to be supported. utf-8 should probably be used as the default encoding for string passwords, rather than ascii. See also #33741

[issue29750] smtplib doesn't handle unicode passwords

Change by R. David Murray : -- stage: -> needs patch versions: +Python 3.8 -Python 3.7 ___ Python tracker <https://bugs.python.org/issue29750> ___ ___ Python-

[issue30820] email.contentmanager.raw_data_manager fails to create multipart messages

R. David Murray added the comment: New changeset 2c071cebe67f517f191f4074757a79b0f597d886 by R. David Murray (Zackery Spytz) in branch 'master': bpo-30820: Remove incorrect docs for email.contentmanager.raw_data_manager (#7631) https://github.com/python/cpyt

[issue30820] email.contentmanager.raw_data_manager fails to create multipart messages

R. David Murray added the comment: New changeset b06fc2d244f95f8a497cbcdc6e2fbeb9b8133ca3 by R. David Murray (Miss Islington (bot)) in branch '3.7': bpo-30820: Remove incorrect docs for email.contentmanager.raw_data_manager (GH-7631) (#7633) https://github.com/python/cpyt

[issue30820] email.contentmanager.raw_data_manager fails to create multipart messages

R. David Murray added the comment: New changeset bbbc3d99dca41bc95a9402d702f6ab833d3003c7 by R. David Murray (Miss Islington (bot)) in branch '3.6': bpo-30820: Remove incorrect docs for email.contentmanager.raw_data_manager (GH-7631) (#7634) https://github.com/python/cpyt

[issue30820] email.contentmanager.raw_data_manager fails to create multipart messages

R. David Murray added the comment: Thanks, Zachery. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33835] Too strong side effect?

Change by R. David Murray : -- status: open -> closed ___ Python tracker <https://bugs.python.org/issue33835> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue33819] Mention "ordered mapping" instead of "ordered dictionary" in email module

R. David Murray added the comment: Message/EmailMessage are intentionally mimicing the full dictionary API, not just the Mapping API (with a couple exceptions and several extensions). But it is important to mention that it is ordered, both for the reason INADA stgtes, and because the text

[issue33844] Writing capital letters with csvwriter.writerow changes the csv file format

R. David Murray added the comment: It doesn't look like this has anything to do with Python. This sounds like a question more appropriate for an Excel help forum. -- nosy: +r.david.murray ___ Python tracker <https://bugs.python.org/is

[issue33846] Misleading error message in urllib.parse.unquote

R. David Murray added the comment: We don't generally do type checks like that. This is a specific case of a general issue with binary operators and mismatched string/bytes types. I thought there was an open issue for it, but I haven't found it yet. -- nosy: +r.da

[issue29750] smtplib doesn't handle unicode passwords

R. David Murray added the comment: While you are correct that latin1 may be common in this situation, I think it may still be better to have utf-8 be the default, since that is the (still emerging? :) standard. However, you are correct to call for examples: if in the *majority* of the real

[issue29750] smtplib doesn't handle unicode passwords

R. David Murray added the comment: For the web cases I presume you also set the password using the web interface, so that doesn't really tell us anything useful. Did you use thunderbird to access the mailbox that you set up via gmail and/or sogo? That would make what thunderbird doe

[issue33879] Item assignment in tuple mutates list despite throwing error

Change by R. David Murray : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33846] Misleading error message in urllib.parse.unquote

R. David Murray added the comment: I thought there was a more general issue for the 'in' operator itself, but perhaps the issue you found was indeed the one I was thinking of. This one certainly seems to be a duplicate of that one ;) If you've a mind to, you could turn th

[issue29750] smtplib doesn't handle unicode passwords

R. David Murray added the comment: We must continue to support at least ascii strings, for backward compatibility reasons. We can certainly improve the error messages, but the goal of this issue is to add support for bytes passwords. I lean toward continuing to only support ascii strings

[issue33890] Pathlib does not compare Windows and MinGW paths as equal

R. David Murray added the comment: Sorry, but these paths are not equal in in any sense that Python by itself can determine. Support for doing this kind of comparison would have to come from MingGW or cygwin, and even if a python library exposed those capabilities, it would be via some new

[issue28710] Sphinx incompatible markup in the standard library

R. David Murray added the comment: Thanks for coming back to this. We're accepting PRs via github now, so the next step now would be to make it into a PR. Sometimes things just get forgotten and you have to nudge them to get them moving (see the devguide for guidelines about when

[issue33893] Linux terminal shortcuts support in python shell

R. David Murray added the comment: zsh lets you edit multiline shell commands as a unit. If you up-arrow, you get all the lines of the block popped up, with the cursor on the last line. Further arrow keys will navigate within the multiline text block, with an up-arrow from the first line

[issue29750] smtplib doesn't handle unicode passwords

R. David Murray added the comment: I didn't think to look at the standards for the auth mechanisms, I only looked at the smtp standards. So, if the standard says utf-8, then we should use that. But we should still support bytes passwords so that an application could work around i

[issue28710] Sphinx incompatible markup in the standard library docstrings

R. David Murray added the comment: Right, my opinion is that we shouldn't be putting markup in docstrings. They are (from our point of view) pure text. I don't know if discussion on python-dev is warranted, it seems like a fairly uncontroversial change, since it brings the doc

[issue28710] Sphinx incompatible markup in the standard library docstrings

R. David Murray added the comment: By the way, in case anyone is curious, I'm pretty sure that markup is left over from the days when tex/latex was what docs were *written* in. -- ___ Python tracker <https://bugs.python.org/is

[issue28710] Sphinx incompatible markup in the standard library docstrings

R. David Murray added the comment: No, it is (somewhat) unique to tex. If you write `word' tex would turn that into a pair of opposing quotes in the typeset document, as opposed to 'word' (the convention in regular text/emails/posts/etc) where you'd just see ascii quote

[issue28710] Sphinx incompatible markup in the standard library docstrings

R. David Murray added the comment: I would still like to see the legacy tex markup removed from the docstrings, so I think closing this issue is not appropriate, but it's not a big enough deal that I'll push for it if Raymond wants to keep

[issue33896] filecmp.cmp returns True on files that differ

R. David Murray added the comment: I understand your concern, but this is working as designed and documented. Using st_ino would mean you would return true if and only if it was the *same* file. That is not the intent. See issue 27396 for some background discussion. -- nosy

[issue33896] filecmp.cmp returns True on files that differ

R. David Murray added the comment: For your problem, just don't use the default shallow setting :) -- ___ Python tracker <https://bugs.python.org/is

[issue33896] Document what components make up the filecmp.cmp os.stat signature.

Change by R. David Murray : -- versions: +Python 2.7 ___ Python tracker <https://bugs.python.org/issue33896> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33896] Document what components make up the filecmp.cmp os.stat signature.

R. David Murray added the comment: I think it might be OK to document what goes in to the signature, but probably in a footnote, as it is somewhat of an implementation detail and could conceivably change. We could then also add a caution about mtime imprecision being a particular risk on

[issue33809] Expose `capture_locals` parameter in `traceback` convenience functions

R. David Murray added the comment: I think we should get one or more of the core devs who were involved in the changes that added that parameter to sign off on whether this is a good idea or not (I have no opinion at the moment). You should be able to find them via git blame and looking at

[issue32500] PySequence_Length() raises TypeError on dict type

R. David Murray added the comment: IIUC that error message came from pypy, not CPython. If you have a reproducer for CPython, you can open a new issue with a request to fix the error message. -- nosy: +r.david.murray ___ Python tracker <ht

[issue33925] builtin_function_or_method compares __self__ by identity instead of equality

R. David Murray added the comment: This is still a duplicate issue, though, you are just arguing for a different resolution of the other one :) -- nosy: +r.david.murray ___ Python tracker <https://bugs.python.org/issue33

[issue33935] shutil.copyfile throws incorrect SameFileError on Google Drive File Stream

R. David Murray added the comment: That patch would cause references to the same file on a google drive to report that the files were different. I'd say this is a bug in Google Drive's posix emulation. I'm not sure there's a good answer here, because even if every other

[issue33935] shutil.copyfile throws incorrect SameFileError on Google Drive File Stream

R. David Murray added the comment: OK. Finding a solution for this (other than never raising samefile on such systems and documenting it as a limitation) may be difficult. -- ___ Python tracker <https://bugs.python.org/issue33

[issue34025] SMTP EmailPolicy not using the correct line length for RCF 2045 encoded data (is 78, should be 76)

R. David Murray added the comment: The default maximum line length is indeed supposed to be 78 (characters..and I can't now remember whether I implemented it in terms of characters or octets), that's per RFC 5322. What is wrong is that content encoded text is supposed to use

[issue34102] local variable 'parts' referenced before assignment in feedparser in email module

R. David Murray added the comment: This appears to be a bug in pip or the ansible-lint package, similar, and possibly identical, to issue 31361. I believe None is being passed in as the argument to feed_parser.feed, which is an invalid use of that API and so correctly results in an error

[issue34104] email.message.get_payload should enforce correct encoding

R. David Murray added the comment: It looks like the virus checkers are not doing robust decoding that the email RFCs recommend, and that thunderbird is. This is obviously a bug in the virus scanners. By default, like thunderbird, the email library does its best to decode attachments. If

[issue34138] imaplib RFC 6855 issue

R. David Murray added the comment: Would you care to propose a patch? That's likely the only way this is going to get fixed, unfortunately, as currently we have no one on the core team interested in imaplib. Which means it is also going to be hard to come up with someone to do the r

[issue34138] imaplib RFC 6855 issue

R. David Murray added the comment: Maybe we'll be luck and Maciej will still be interested :) -- nosy: +maciej.szulik ___ Python tracker <https://bugs.python.org/is

[issue34155] email.utils.parseaddr mistakenly parse an email

R. David Murray added the comment: That does appear to be a bug. Note that the new email API handles it correctly: >>> x = """ ... > From: =?utf-8?Q?z...@redacted.com.cn=E3=82=86=E2=86=91=E3=82=86?= ... =?utf-8?Q?=E3=82=83=E3=82=85=E3=81=87=E3=8

[issue34155] email.utils.parseaddr mistakenly parse an email

R. David Murray added the comment: Oops, I left out a step in that cut and paste. For completeness: >>> x = x[3:] -- ___ Python tracker <https://bugs.python.or

[issue34155] email.utils.parseaddr mistakenly parse an email

R. David Murray added the comment: Ah, maybe it doesn't handle it completely correctly; that decode looks different now that I look at it in detail. -- ___ Python tracker <https://bugs.python.org/is

<    31   32   33   34   35   36   37   38   39   40   >