[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

R. David Murray added the comment: All of which isn't to discount that you might have a found a bug, by the way, if you want to investigate further :) -- ___ Python tracker <https://bugs.python.org/is

[issue39073] email incorrect handling of crlf in Address objects.

R. David Murray added the comment: Hmm. Yes, \r\n should be disallowed in the arguments to Address. I thought it already was, so that's a bug. That bug produces the other apparent bug as well: because the X: was treated as a separate line, the previous header did not need double q

[issue39040] Wrong attachement filename when mail mime header was too long

R. David Murray added the comment: One more tweak to the test and we'll be good to go. -- ___ Python tracker <https://bugs.python.org/issue39040> ___ ___

[issue39131] signing needs two serialisation passes

R. David Murray added the comment: Ideally this should be exposed by extending the content manager. Instantiating MIME classes is part of the old API, not the new. The code in the PR may well be correct, but class should be hidden from the normal user (of the new API). I'm not sure

[issue39040] Wrong attachement filename when mail mime header was too long

R. David Murray added the comment: I don't see the change to the test in the PR. Did you miss a push or is github doing something wonky with the review? (I haven't used github review in a while and I had forgetten how hard it

[issue23147] Possible error in _header_value_parser.py

R. David Murray added the comment: Thanks for the ping. Whether or not Serhiy's patch fixed the original problem, the algorithm rewrite has happened so this issue is no longer relevant in any case. -- stage: test needed -> resolved status: open -

[issue23434] support encoded filename in Content-Disposition for HTTP in cgi.FieldStorage

R. David Murray added the comment: Are you saying there is no (http) RFC compliant way to fix this, or no way to fix it with the email library parsers? If the latter, the library is pretty flexible and for internal stdlib use it would probably be permissible to directly call methods in the

[issue39384] Email parser creates a message object that can't be flattened as bytes.

R. David Murray added the comment: Since you parsed it as a string it is not really legitimate to serialize it as bytes. (That will work if the input message only contains ascii, but not if it contains unicode). You'll get the same error if you replace the garbage with the "

[issue39309] Please delete my account

R. David Murray added the comment: AFAIR it can only be done using the roundup command line on the server. -- nosy: +ezio.melotti ___ Python tracker <https://bugs.python.org/issue39

[issue24337] Implement `http.client.HTTPMessage.__repr__` to make debugging easier

R. David Murray added the comment: Thanks for the PR, but I've noted an issue on the review. In any case we should agree on what goes in the repr here in this issue before actually implementing anything. -- ___ Python tracker &

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

R. David Murray added the comment: Please open a new issue for this question. -- ___ Python tracker <https://bugs.python.org/issue10740> ___ ___ Python-bug

[issue39384] Email parser creates a message object that can't be flattened as bytes.

R. David Murray added the comment: If we can get an actual reproducer using message_as_bytes I'd feel more comfortable with the fix. I worry that there is some other bug this is exposing that should be fixed instead. -- ___ Python tr

[issue39384] Email parser creates a message object that can't be flattened as bytes.

R. David Murray added the comment: message_from_bytes -- ___ Python tracker <https://bugs.python.org/issue39384> ___ ___ Python-bugs-list mailing list Unsub

[issue39771] EmailMessage.add_header doesn't work

R. David Murray added the comment: I think you are saying that you want the charset in the encoded filename to be GBK rather than utf-8? utf-8 should certainly display correctly in your email client, though, so if it is not there is something else going wrong. As far as the 3 tuple not

[issue39771] EmailMessage.add_header doesn't work

R. David Murray added the comment: Actually, given that the contentmanager does accept a charset parameter for text content, it does seem reasonable to treat this as a bug. But as I said fixing it may not be trivial. -- ___ Python tracker

[issue39771] EmailMessage.add_header doesn't work

R. David Murray added the comment: The legacy API appears to be using an RFC-incorrect (but common) encoded-word encoding, while the new API is using the RFC-compliant MIME-parameter encoding (% encoding). Which email client are you using

[issue39771] EmailMessage.add_header doesn't work

R. David Murray added the comment: Since Outlook is one of the mailers that generates the non-RFC-compliant headers, it doesn't surprise me all that much that it can't interpret the RFC compliant headers correctly. I'm not sure there is anything we can do here. I suppose som

[issue39757] EmailMessage bad encoding for international domain

R. David Murray added the comment: This is not actually a duplicate of 11783. Rereading (parts of) that issue, we decided we currently have no good way to do automatic conversion between unicode and internationalized domains, so the user of the library has to do it themselves. This means

[issue39793] make_msgid fail on FreeBSD 12.1-RELEASE-p1 with different domains

R. David Murray added the comment: I don't object to this patch, but that sure looks like a broken system. -- ___ Python tracker <https://bugs.python.org/is

[issue39771] EmailMessage may need to support RFC-non-compliant MIME parameter encoding (encoded words in quotes) for output.

R. David Murray added the comment: I actually agree: if most (by market share) MUAs handle the RFC-incorrect parameter encoding style, and a significant portion does not handle the RFC correct style, then we should support the de-facto standard rather than the official standard as the

[issue27793] Double underscore variables in module are mangled when used in class

R. David Murray added the comment: You are welcome to open a doc-enhancement issue for the global docs. For the other, as noted already if you want to advocate for a change to this behavior you need to start on python-ideas, but I don't think you will get any traction. Another pos

[issue39073] email incorrect handling of crlf in Address objects.

R. David Murray added the comment: Thanks for the PR. I've made some review comments. -- ___ Python tracker <https://bugs.python.org/issue39073> ___ ___

[issue39966] mock 3.9 bug: Wrapped objects without __bool__ raise exception

R. David Murray added the comment: My guess is that it isn't so much that __bool__ is special, as that the evaluation of values in a boolean context is special. What you have to do to make a mock behave "correctly" in the face that I'm not sure (I haven't inves

[issue39073] email incorrect handling of crlf in Address objects.

R. David Murray added the comment: New changeset 614f17211c5fc0e5b828be1d3320661d1038fe8f by Ashwin Ramaswami in branch 'master': bpo-39073: validate Address parts to disallow CRLF (#19007) https://github.com/python/cpython/commit/614f17211c5fc0e5b828be1d332066

[issue39073] email incorrect handling of crlf in Address objects.

R. David Murray added the comment: Thanks! -- ___ Python tracker <https://bugs.python.org/issue39073> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39073] email incorrect handling of crlf in Address objects.

Change by R. David Murray : -- stage: patch review -> backport needed ___ Python tracker <https://bugs.python.org/issue39073> ___ ___ Python-bugs-list mai

[issue40359] email.parse part.get_filename() fails to unwrap long attachment file names (legacy API)

R. David Murray added the comment: Yeah, that looks like a bug in the old API. If you try the new API, it does the right thing. To do that, import email.policy and make your message_as_string call: email.message_from_string(raw, policy=email.policy.default) Note, however, that you

[issue40359] email.parse part.get_filename() fails to unwrap long attachment file names (legacy API)

R. David Murray added the comment: As far as I know you currently still have to specify the policy. It was, yes, intended that 'default' become the actual default. I could have sworn there was an open issue for doing this, but I can't find it. I remember having a co

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

R. David Murray added the comment: The PR looks good to me, but I describe the change differently. I'm not sure how I missed this in the original implementation, since I obviously checked it for the 8bit case. Too long ago to rem

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

R. David Murray added the comment: New changeset 6f2f475d5a2cd7675dce844f3af436ba919ef92b by Arkadiusz Hiler in branch 'master': bpo-40597: email: Use CTE if lines are longer than max_line_length consistently (gh-20038) https://github.com/python/cpyt

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

R. David Murray added the comment: Thanks, Arkadiusz. -- resolution: -> fixed stage: patch review -> backport needed versions: -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker <https://bugs.python.org/i

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

R. David Murray added the comment: New changeset c1f1ddf30a595c2bfa3c06e54fb03fa212cd28b5 by Miss Islington (bot) in branch '3.8': bpo-40597: email: Use CTE if lines are longer than max_line_length consistently (gh-20038) (gh-20084) https://github.com/python/cpyt

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

Change by R. David Murray : -- stage: backport needed -> resolved ___ Python tracker <https://bugs.python.org/issue40597> ___ ___ Python-bugs-list mai

[issue42484] get_obs_local_part fails to handle empty local part

R. David Murray added the comment: Yep, you've found another in a category of bugs that have shown up in the parser: places where there is a missing check for there being any value at all before checking character [0]. In this case, the fix should be to add if not obs_local

[issue42433] mailbox.mbox fails on non ASCII characters

R. David Murray added the comment: After thinking about it some more, I think given that when there is no non-ascii mbox will happily treat *anything* as valid on the "From " line, that we should consider blowing up on non-ascii t

[issue43061] subprocess: feature request: Get only the stdout of the last shell command

R. David Murray added the comment: This has nothing to do with python other than the fact that you are using it to capture stdout. You have to figure out how to get the output you want to be what shows up on stdout, python has no knowledge of what commands you put in your shell script, and

[issue43090] parseaddr (from email.utils) returns invalid input string instead of ('', '')

R. David Murray added the comment: The return value is correct. Interpreted as an email address, 'randomstring' is a local mailbox. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Pyt

[issue39040] Wrong attachement filename when mail mime header was too long

R. David Murray added the comment: New changeset 21017ed904f734be9f195ae1274eb81426a9e776 by Abhilash Raj in branch 'master': bpo-39040: Fix parsing of email mime headers with whitespace between encoded-words. (gh-17620) https://github.com/python/cpyt

[issue41023] smtplib does not handle Unicode characters

R. David Murray added the comment: If you use the 'sendmail' function for sending, then it is entirely your responsibility to turn the email into "wire format". Unicode is not wire format, but if you give sendmail a string that only has ascii in it it nicely converts

[issue41206] behaviour change with EmailMessage.set_content

R. David Murray added the comment: I'm short of time, if someone could approve Mark's PR and merge it it would be great. There wasn't supposed to be any behavior change other than the one documented in #40597. -- ___ Python

[issue41145] EmailMessage.as_string is altering the message state and actually fix bugs

R. David Murray added the comment: The as_strings docs say: "Flattening the message may trigger changes to the Message if defaults need to be filled in to complete the transformation to a string (for example, MIME boundaries may be generated or modified)." So, while this is ind

[issue41387] Escape needed in the email documentation example

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

[issue41402] email: ContentManager.set_content calls nonexistent method encode() on bytes

R. David Murray added the comment: The fix looks good to me. Don't know how I made that mistake, and obviously I didn't write a test for it... -- ___ Python tracker <https://bugs.python.o

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

R. David Murray added the comment: It's not really an abuse. It is, however, buggy. It should be being applied *only* when the header contains unstructured text. Unfortunately I made the choice to treat any header that doesn't have a specific parser as unstructured, and that w

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

R. David Murray added the comment: Yes for the registry changes. I thought we had fixed the bug that was causing message-id to get encoded, but maybe it still exists in 3.7? I don't remember when we fixed it (and I may be remembering wrong!) As for X- "unstructured header

[issue42433] mailbox.mbox fails on non ASCII characters

R. David Murray added the comment: The problem with that archive is that it is not in proper mbox format. It contains the following line (5689): From here I was hoping to run something like “dbus-send –system –dest=Test.Me –print-reply /Japan Japan.Reset.Test string:”Hello”” You will

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: No, it wouldn't. I expect "{}".format(x) to produce something for an arbitrary x. Breaking that would break a fundamental Python contract. Improving the error message for 'd' is more possible. Perhaps "the format c

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: Oh, and when you say there is nothing in the documentation about the 's' case for arbitrary objects, it is made clear in various places that every object has an str, which defaults to its repr if it has no specific __str__. Combine that

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: "an empty format string" is exactly what I was talking about. Putting nothing between the {}'s is an empty format string. I can't think of any way to make that wording clearer. The format docs should not contains examples of the

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: Good point. That should be fixed. It should be "empty format specification". -- ___ Python tracker <http://bugs.python.o

[issue12600] Support parameterized TestCases in unittest

R. David Murray added the comment: Meaning you want to run the same test suite with a variety of different DB connections? That seems like a reasonable use case. Personally I find that while I sometimes create subclasses to adjust certain class parameters (thus creating a parameterized test

[issue12600] Support parameterized TestCases in unittest

R. David Murray added the comment: Drat, the tracker lost my post. In summary, given a concrete use case (running a test case with a variety of different DB connections) and the improved readablility for the common case of just changing class constants in the 'parameterized' subcl

[issue12600] Support parameterized TestCases in unittest

R. David Murray added the comment: Maybe we could add a recipe for doing this to the load_tests docs? I don't think that load_tests is going to be more readable, though, since it doesn't allow you to put the parameterization next to the class you are parameterizing (unless y

[issue12600] Support parameterized TestCases in unittest

R. David Murray added the comment: That's not the kind of parameterization this ticket is about, though. You are talking about passing data in to a test run from the command line (or other source), which is a different issue (though the implementations might share some common infrastru

[issue12600] Support parameterized TestCases in unittest

R. David Murray added the comment: I'd still like to see a recipe for creating parameterized test cases via load_tests added to the docs. It may be relatively obvious how to do it once you think of it, but it isn't obvious to a relative newcomer that you *can* do it, and it wo

[issue13826] Having a shlex example in the subprocess.Popen docs is confusing

Changes by R. David Murray : -- priority: normal -> low ___ Python tracker <http://bugs.python.org/issue13826> ___ ___ Python-bugs-list mailing list Unsubscri

[issue13826] Having a shlex example in the subprocess.Popen docs is confusing

R. David Murray added the comment: It is not particularly intuitive what goes in to a Popen non-shell argument list, unless you are an experienced programmer. The real purpose of the note is to convey a lot of information about how tokenization works in a short example, and it also

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: Oh, I see. Yes, that is a problem. object.__format__ knows the type of the object it was called on, right? Couldn't it catch the error and re-raise it with the correct type? (If the type isn't str, of course, we don't want to get i

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: Oh, never mind that comment about recursion, I wasn't thinking it through. -- ___ Python tracker <http://bugs.python.org/is

[issue13790] In str.format an incorrect error message for list, tuple, dict, set

R. David Murray added the comment: So the error is going to be something about the source type not supporting '__format__'? That change will also address the OP's concern about truncated reprs when a fixed string length is specified, so I agree that the title issue can be c

[issue13849] Add tests for NUL checking in certain strs

R. David Murray added the comment: Adding tests helps the other VMs, which generally are trailing behind the CPython releases. -- nosy: +r.david.murray ___ Python tracker <http://bugs.python.org/issue13

[issue13849] Add tests for NUL checking in certain strs

R. David Murray added the comment: My understanding (and recollection, but I don't have notes I can point at to hand) is that one goal that arose from recent VM and language summits was for the CPython test suite to be used as the validating test suite, with CPython-specific tests mark

[issue13849] Add tests for NUL checking in certain strs

R. David Murray added the comment: Oh, and in case it isn't clear, this request is *coming* from one of the other VMs (pypy), so if my summit recollection is correct, they are in fact "adding a test that they need" by submitting this issue :) (Or at least they will have once

[issue13875] cmd: no user documentation

R. David Murray added the comment: Well, since it isn't limited to interactive use, I don't think 'interactive' is missing. MOTW links are a more global issue that was discussion on python-dev (I forget the outcome, but I think it was "no"). I don't see an

[issue13875] cmd: no user documentation

R. David Murray added the comment: You can feed a cmd driven interface from stdin or via cmd.onecmd. However, I agree that the intended and primary use case is interactive. There wouldn't be much point in using cmd if the primary intent of your program wasn't i

[issue13906] mimetypes.py under windows - bad exception catch

R. David Murray added the comment: This is a duplicate of issue 9291. -- nosy: +r.david.murray resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> mimetypes initialization fails on Windows because of non-Latin characters

[issue11457] os.stat(): add new fields to get timestamps as Decimal objects with nanosecond resolution

R. David Murray added the comment: There is also the fact that we have traditionally exposed thin wrappers around posix functions (and then were practical provided Windows emulations). We aren't 100% consistent about this, but we are pretty consistent abo

[issue13846] Add time.monotonic() function

R. David Murray added the comment: If you are trying to time something (an interval), having the time go backward can really screw up your data. And that *will* happen on a system that is running NTP (or even just resets its time). monotonic clocks were introduced at the OS level for a

[issue13936] datetime.time(0, 0, 0) evaluates to False despite being a valid time

R. David Murray added the comment: I don't think I would have ever thought of testing a datetime for its truth value. But the behavior you observe is consistent with the rest of Python: 0 is false. I wonder if this is by design or by accident. -- nosy: +r.david.m

[issue13936] datetime.time(0, 0, 0) evaluates to False despite being a valid time

Changes by R. David Murray : -- nosy: +belopolsky ___ Python tracker <http://bugs.python.org/issue13936> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13952] mimetypes doesn't recognize .csv

R. David Murray added the comment: Yes, but text/tab-delimited-values/.tsv is older. .tsv dates from the days of Gopher, but text/csv was formalized only in October of 2005. Presumably nobody has asked for it before, for some odd reason. Now we get to debate again whether updating

[issue13952] mimetypes doesn't recognize .csv

R. David Murray added the comment: As far as I know having it mirror the IANA registry is the intent (there's a comment in the module that can be read as implying that). So I'd be inclined to treat this one as a bug and fix it in 2.7 and 3.2 as well as 3.3. I'm not sure w

[issue13952] mimetypes doesn't recognize .csv

R. David Murray added the comment: Ah, analagous to the way keyword.py regenerates its embedded table based on the actual python grammar? Yes, that would be nice. -- ___ Python tracker <http://bugs.python.org/issue13

[issue13955] email: RFC 2822 has been obsoleted by RFC 5322

R. David Murray added the comment: 5322 is still a draft, according to the IETF. That said, we are paying attention to 5322. -- nosy: +r.david.murray resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Pytho

[issue13957] parsedate_tz doesn't distinguish -0000 from +0000

R. David Murray added the comment: This is fixed already in 3.3. It is a behavior change that could theoretically cause some problems. Currently, you can think of None as meaning "there was no timezone info at all", which is subtly different from -, which means "this tim

[issue13968] Support recursive globs

R. David Murray added the comment: I have to say that the non-obvious subtleties you point out in your rglob make me think I personally would probably opt to use Nick's module directly instead, so that I was sure what I was getting. -- nosy: +r.david.m

[issue13968] Support recursive globs

R. David Murray added the comment: Hmm. Just to make it clear where I'm coming from, though, I should also point out that I use rdiff-backup, which uses the **/yadayada syntax, and I hate it any time I have to try to figure out what such a glob is going to actually

[issue13968] Support recursive globs

R. David Murray added the comment: How about having separate starting path and glob arguments, where the glob cannot contain any directory? I'm -1 on this function as it stands. My vote could change if the final semantics are intuitive and unambiguous. (It's OK if getting t

[issue13968] Support recursive globs

R. David Murray added the comment: So given /home/a /home/a/k.py /home/a/c/j.py /home/b/z.py /home/b/c/f.py and a current directory of /home/a, we'd have: pattern matches --- --- *.py k.py, c/j.py c/*.pyc/j.py c*

[issue1559549] ImportError needs attributes for module and file name

R. David Murray added the comment: On the drive home...are you borrowing one of Google's self driving cars? :) -- ___ Python tracker <http://bugs.python.org/issu

[issue13968] Support recursive globs

R. David Murray added the comment: Well, in that case I would expect that the argument 'c/*.py' would start walking in the c directory, but I definitely did not get that impression from Antoine's explanation of how the function works. I again advocate separating th

[issue13980] getcwd problem does not return cwd

R. David Murray added the comment: That's just how function definitions in Python work. The prototype is evaluated when the function is defined, not when it is run, so the default value of path will always be the value of getcwd at the time the function *defintion* is done (which

[issue13968] Support recursive globs

R. David Murray added the comment: I don't know, is it? From what has been said so far I'd expect */c/d/*.py to look for *.py files in all c/d subdirectories of direct subdirectories of the current directory, and subdirectories of those c/d directories. But I wouldn't

[issue13968] Support recursive globs

R. David Murray added the comment: @antoine: no, my description involves recursion. It assumes that the path portion of the glob specifies the directories to *start* from, but that the filename glob portion then applies recursively to any of those start directories. The alternative

[issue13968] Support recursive globs

R. David Murray added the comment: Oh, yeah, and there's still the question of whether or not directories are matched by the terminal glob pattern, which I would naively expect they would be, in either interpretation, but I wouldn'

[issue13968] Support recursive globs

R. David Murray added the comment: Ah, OK, so what you are saying is that rglob returns the concatenation of the results of running ls with the argument glob in each subdirectory of a walk starting with the current directory, except that the returned names have paths anchored in the current

[issue1559549] ImportError needs attributes for module and file name

R. David Murray added the comment: However you do it, I'm very much in favor of having the full name available. I either wrote or fixed (I can't remember which) that stack walk in pydoc, and you are right, it is very very ugly. This would also be a big benefit for unittest, which

[issue13952] mimetypes doesn't recognize .csv

R. David Murray added the comment: On Windows we do (now) read from the registry as well. My guess is there are a lot more Windows systems out there with outdated registries then there are unix systems with outdated /etc/mime files, though

[issue13968] Support recursive globs

R. David Murray added the comment: The last forumulation of what rglob does "apply the glob to the current directory and all subdirectories recursively, returning the joined list with filenames anchored in the current directory" is simple and intuitive enough for me. (I'm not

[issue13955] email: RFC 2822 has been obsoleted by RFC 5322

R. David Murray added the comment: Hmm. I misread this. You are, in fact correct, but I don't think there is anything comprehensive to do here. As I make changes and have actually checked then against RFC 5322, I'm either changing or adding that RFC number to the comment

[issue8739] Update to smtpd.py to RFC 5321

R. David Murray added the comment: Alberto, might you still interested in working on this? I thought I'd do a quick update to current trunk and check it in, but in the process of doing that I found some issues. I suspect it has been frustrating for you that nothing happened with thi

[issue8739] Update to smtpd.py to RFC 5321

R. David Murray added the comment: Gah, that's what I get for trying to do something quick. By changing the name of that variable I introduced a backward incompatibility, since that change was released in 3.2. -- ___ Python tracker

[issue8739] Update to smtpd.py to RFC 5321

R. David Murray added the comment: OK. Maybe someone else will want to work on it, too. I'll see if I can get it taken care of one way or another during the PyCon sprints. I'm going to mark this as easy, because really other than expanding test coverage I think the only thing

[issue14003] __self__ on built-in functions is not as documented

R. David Murray added the comment: It looks like this changed between 2.x and 3.x but the docs were not updated. None makes more sense than the module as __self__, though, so perhaps it is actually a bug. Then, again, since Python functions don't have a __self__, the __self__ of bui

[issue13927] Extra spaces in the output of time.ctime

R. David Murray added the comment: Or you could give the strftime specification string that produces the equivalent output. -- nosy: +r.david.murray ___ Python tracker <http://bugs.python.org/issue13

[issue13881] Stream encoder for zlib_codec doesn't use the incremental encoder

Changes by R. David Murray : -- nosy: +haypo ___ Python tracker <http://bugs.python.org/issue13881> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14016] Usage of socket.sendall() in multiple threads

R. David Murray added the comment: This isn't really the place to get help on using python, but no, python doesn't do any implicit locking for you. -- nosy: +r.david.murray resolution: -> invalid status: open -> closed ___ Pytho

[issue14025] unittest.TestCase.assertEqual does not show diff when comparing str with unicode

R. David Murray added the comment: The latter is arguably a bug. The former is working as designed, as far as I know. In Python3 bytes and string do not compare equal. -- nosy: +michael.foord, r.david.murray ___ Python tracker <h

[issue14025] unittest.TestCase.assertEqual does not show diff when comparing str with unicode

R. David Murray added the comment: In case it isn't clear, by "arguably a bug" I mean in a theoretical sense. Even if Michael agrees with me we can't change the fact that 2.7 unittest treats str and unicode with the same content as equal. For the other it might have been

[issue14031] logging module cannot format str.format log messages

R. David Murray added the comment: That can't work. The logging messages may come from libraries written by someone else, using % formatting. The style has to be set at the individual logger level. -- nosy: +r.david.murray, vinay.

<    19   20   21   22   23   24   25   26   27   28   >