[issue35701] [uuid] 3.8 breaks weak references for UUIDs

Change by David Heiberg : -- pull_requests: +11374, 11375 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issue35701> ___ ___ Py

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

Change by David Heiberg : -- pull_requests: +11374, 11375, 11376 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

David Heiberg added the comment: Agreed. I will fix the documentation and submit a PR this weekend hopefully. -- ___ Python tracker <https://bugs.python.org/issue35

[issue30212] test_ssl.py is broken in Centos7

David Antonio Garcia Campos added the comment: Hello Victor, I just saw your message. I will try to setup my enviorment and will come back to you. BR David Garcia -- nosy: +David Antonio Garcia Campos ___ Python tracker <https://bugs.python.

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

David Heiberg added the comment: Should the note on arbitrary attributes also be removed? If this was documented previously then I don't see the need for it here, but if this has never been documented then maybe some other way of wording it may be sensible to include

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

David Heiberg added the comment: Ahh yes of course, I will remove that from the notes. With regards to the second note, would it do any harm to leave it in? I suppose it does imply that this was possible before... -- ___ Python tracker <ht

[issue35753] Importing call from unittest.mock directly causes ValueError

David Antonini added the comment: Apologies for initial malformed message, I hit submit prematurely. -- ___ Python tracker <https://bugs.python.org/issue35

[issue35753] Importing call from unittest.mock directly causes ValueError

David Antonini added the comment: I'm having a problem with mock.call when I import it directly from unittest.mock. When I do: from unittest.mock import patch, mock_open, call mocked_print.assert_has_calls([ call("first print"), call("second print"), ])

[issue35753] Importing call from unittest.mock directly causes ValueError

New submission from David Antonini : Ok so that's a pretty odd bug. I already had from unittest.mock import patch, mock_open so I simply modified that to from instead of doing mock.call in my test. Changing this to from unittest import mock and then mock.call fixed the error. from

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

Change by David Heiberg : -- keywords: +patch, patch, patch pull_requests: +11236, 11237, 11238 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

Change by David Heiberg : -- keywords: +patch, patch pull_requests: +11236, 11237 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

Change by David Heiberg : -- keywords: +patch pull_requests: +11236 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

David Heiberg added the comment: Ok thanks for your input, I will work on a PR and hopefully submit one tomorrow or Wednesday depending on schedule. -- ___ Python tracker <https://bugs.python.org/issue35

[issue35701] [uuid] 3.8 breaks weak references for UUIDs

David Heiberg added the comment: Since there has been no objection to this yet, would it be alright for me to take this as my first PR? On top of the change you mentioned to the __slots__ list, should there also be a test written so that a similar regression doesn't happen again

[issue35726] QueueHandler formating affects other handlers

New submission from David Ruggles : ISSUE: if you add a formatter to QueueHandler any subsequently added handlers will get the formatting added to QueueHandler CAUSE: as best as I can tell, the code here: https://github.com/python/cpython/blob/d586ccb04f79863c819b212ec5b9d873964078e4/Lib

[issue35715] ProcessPool workers hold onto return value of last task in memory

Change by David Chevell : -- keywords: +patch, patch pull_requests: +11075, 11076 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35715] ProcessPool workers hold onto return value of last task in memory

Change by David Chevell : -- keywords: +patch, patch, patch pull_requests: +11075, 11076, 11077 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35715] ProcessPool workers hold onto return value of last task in memory

Change by David Chevell : -- keywords: +patch pull_requests: +11075 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35715> ___ ___ Py

[issue35715] ProcessPool workers hold onto return value of last task in memory

Change by David Chevell : -- keywords: +patch, patch, patch, patch pull_requests: +11075, 11076, 11077, 11078 stage: -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue35715] ProcessPool workers hold onto return value of last task in memory

New submission from David Chevell : ProcessPoolExecutor workers will hold onto the return value of their last task in memory until the next task is received. Since the return value has already been propagated to the parent process's `Future` or else effectively discarded, this is holding

[issue35486] subprocess module import hooks breaks back compatibility

David Wilson added the comment: Hi Nick, The purpose of ModuleNotFoundError is clear and unrelated to the problem documented here. The problem is that due to the introduction of ModuleNotFoundError, ImportError's semantics have been changed within a minor release in a breaking, backwards

[issue33084] Computing median, median_high an median_low in statistics library

David Mertz added the comment: I believe that the current behavior of `statistics.median[|_low|_high\]` is simply broken. It relies on the particular behavior of Python sorting, which only utilizes `.__lt__()` between objects, and hence does not require a total order. I can think

[issue4696] email module does not unfold headers

R. David Murray added the comment: The new email API is no longer provisional. It isn't the *default* yet, but it isn't provisional. So yes, this is resolved. Cheryl, if you see places in the current docs that still say provisional, please open an issue to remove those

[issue35625] Comprehension doc doesn't mention buggy class scope behavior

Change by R. David Murray : Removed file: https://bugs.python.org/file48026/keyfile.png ___ Python tracker <https://bugs.python.org/issue35625> ___ ___ Python-bugs-list m

[issue35625] Comprehension doc doesn't mention buggy class scope behavior

Change by R. David Murray : -- components: -email nosy: -barry, r.david.murray type: security -> behavior ___ Python tracker <https://bugs.python.org/issu

[issue35611] open doesn't call IncrementalEncoder with final=True

New submission from David Haney : The implementation of open relies on a codecs' IncrementalEncoder, however it never calls `encode` with final=True. This appears to violate the documentation for IncrementalEncoder.encode which states that the last call to encode _must_ set final=True

[issue35547] email.parser / email.policy does not correctly handle multiple RFC2047 encoded-word tokens across RFC5322 folded headers

R. David Murray added the comment: Here's a patch that makes the example work correctly. This is not a fix, a real fix will be more complicated. This just demonstrates the kind of thing that needs fixing and where. The existing parser produces a sub-optimal parse tree as its result

[issue35486] subprocess module breaks backwards compatibility with import hooks

David Wilson added the comment: Having considered this for a few hours, it seems the following is clear: - 3.6 introduces ModuleImportError - 3.7 begins using it within importlib - 3.8 first instance of stdlib code catching it - PEP-302 and PEP-451 are the definitive specifications for how

[issue35486] subprocess module breaks backwards compatibility with import hooks

Change by David Wilson : -- title: subprocess module breaks backwards compatibility with older import hooks -> subprocess module breaks backwards compatibility with import hooks ___ Python tracker <https://bugs.python.org/issu

[issue35486] subprocess module breaks backwards compatibility with older import hooks

David Wilson added the comment: Corrected GitHub link for the commit: https://github.com/python/cpython/commit/880d42a3b24 -- ___ Python tracker <https://bugs.python.org/issue35

[issue35486] subprocess module breaks backwards compatibility with older import hooks

New submission from David Wilson : The subprocess package since 880d42a3b24 / September 2018 has begun using this idiom: try: import _foo except ModuleNotFoundError: bar However, ModuleNotFoundError may not be thrown by older import hook implementations, since that subclass was only

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: Ah, got it (and see the pipelines comment by Steve). Jeremy, I suspect you might actually be able to restart the most recent 3.6 builds on my builders since you were the committer. It changed in Sep to only allow python-core users and the "owner" of

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: Oh, it's not the installation itself, I'm just wondering if allowing a newer version is ok too? Of course, it doesn't preclude expanding the build script in the future, so I've installed 15063 to both Win8/10 workers. I don't currently have access to restart

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: Hmm, VS2015 started as a full installation (with UI), probably right from its initial release. The build tools only installation (v141) is for VS2017. Best I can tell I'm at update 1 - my update version in the registry is 14.0.24720 (plus I have a .1

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: (and the working log) -- Added file: https://bugs.python.org/file47986/msbuild-win10-good.log ___ Python tracker <https://bugs.python.org/issue35

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: > So before the change, the 16299 SDK wasn't being detected either, but perhaps > the 10240 one was? So I'm just confused It does seems likely that 10240 of the UCRT was being used (based on the attached msbuild logs). Howevr, the UCRT w

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: (sorry for the rapid updates) I'm also fairly sure that none of my workers have update 3 for VS2015. They do however all have VS2017 - but I think VS2015 still gets picked for 3.6 if both are present, right? So that's another variable, in that my workers

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: Oh, since my reading comprehension must be low today, it appears like Jeremy actually had a closer situation previously as I'm in now, with a later (not older) version of the SDK that wasn't in the list. Which is interesting, since he got an error about

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: Well, correct me if I'm wrong, but installing 15063 would then match one of the checks, and become the selected SDK, so be expected to work fine, right? I think (not sure) that the issue with my Win8/10 workers is they only have the later 16299. So

[issue35433] Correctly detect installed SDK versions

David Bolen added the comment: I'm not that familiar (ok, at all) with the build process configuration, but in looking at the changes to python.props, it appears to now enforce the minimum in the build process regardless of whether it is found, whereas before the build tool was allowed

[issue35448] ConfigParser .read() - handling of nonexistent files

Change by David Heiberg : -- nosy: +dheiberg ___ Python tracker <https://bugs.python.org/issue35448> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35403] support application/wasm in mimetypes and http.server

R. David Murray added the comment: We don't generally add a mime type until it is a de-jure or de-facto standard. If it is still in testing it is probably too soon to add it. For testing, you can always add it yourself in your code via the api that mimetypes provides

[issue25545] email parsing docs: clarify that only ASCII strings are supported

R. David Murray added the comment: The problem comes from thinking you can parse an arbitrary email message if it is in unicode form. *YOU CANNOT DO THAT* in the general case (ie: non-ascii attachments). That said, the new email package API is designed to facilitate "off label"

[issue31715] Add mimetype for extension .mjs

R. David Murray added the comment: We have generally made an exception to the "new feature" rule for mimetypes. That is, we don't really consider a mimetype addition to be a new feature in the sense that our backward compatibility rules mean. It is true that an application

[issue35369] List sorting makes duplicate comparisons

David Wyde added the comment: Okay. Thanks! -- ___ Python tracker <https://bugs.python.org/issue35369> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35369] List sorting makes duplicate comparisons

David Wyde added the comment: Thanks for the speedy and helpful response. Keeping complexity down is fair. The wasted if-checks on subsequent iterations are certainly a negative trade-off. I saw that binarysort() is only called in one place, but I understand wanting to keep it generic. I

[issue35369] List sorting makes duplicate comparisons

Change by David Wyde : Added file: https://bugs.python.org/file47963/sort.py ___ Python tracker <https://bugs.python.org/issue35369> ___ ___ Python-bugs-list mailin

[issue35369] List sorting makes duplicate comparisons

New submission from David Wyde : Python's Timsort sometimes makes the same comparison twice. This leads to extra compares, which can hurt performance. Python sorts several length-3 permutations in 4 steps, and the problem accumulates with bigger data. There are ~9,800 duplicate less-than

[issue35350] importing "ctypes" immediately causes a segmentation fault

David added the comment: Another small update: After I recompiled Python with the commented out statement, I did a small test if loading a shared library works. I compiled the following test function to testib.so: #include void test_func(void); void test_func(void) { printf

[issue35350] importing "ctypes" immediately causes a segmentation fault

David added the comment: Small update: After commenting out Py_XDECREF(self->restype) in function CThunkObject_dealloc(PyObject *_self), I can import ctypes without getting a segmentation fault. static void CThunkObject_dealloc(PyObject *_self) { CThunkObject *self = (CThunkObj

[issue35350] importing "ctypes" immediately causes a segmentation fault

New submission from David : ~Environment Cross compiled Python 2.7.15 for ARM Cortex-A7 target, Linux Kernel 4.18 uname -a: Linux Test-0002 4.18.13 #1 SMP Wed Oct 31 11:20:07 CET 2018 armv7l GNU/Linux ~Description of the problem Importing the "ctypes" module in order to l

[issue30681] email.utils.parsedate_to_datetime() should return None when date cannot be parsed

R. David Murray added the comment: Reported again in issue #35342. The existing PR is close to complete, but needs adjusted for the fact that we want (and want to document) that the utility raises errors (ie: catch the error in the header parser rather than having the utility return None

[issue35342] email "default" policy raises exception iterating over unparseable date headers

R. David Murray added the comment: This is effectively a duplicate of #30681, which has a solution, although it is not yet in final form per the last couple of comments on the issue and the PR. -- resolution: -> duplicate stage: -> resolved supe

[issue35338] set union/intersection/difference could accept zero arguments

New submission from David Miguel Susano Pinto : set union, intersection, difference methods accept any non-zero number of sets and return a new set instance, like so: >>> a = set([1, 2]) >>> b = set([1, 3]) >>> c = set([3, 5]) >>> set.u

[issue24925] Allow doctest to find line number of __test__ strings if formatted as a triple quoted string.

R. David Murray added the comment: Without looking at doctest.py, yes. I believe the doctests in that file should be already plugged in to the unittest framework, so adding new testcase containing a non-doctest unit test should work fine

[issue27240] 'UnstructuredTokenList' object has no attribute '_fold_as_ew'

R. David Murray added the comment: No. 3.5 is in security-fix-only mode. -- ___ Python tracker <https://bugs.python.org/issue27240> ___ ___ Python-bugs-list m

[issue35251] FTPHandler.ftp_open documentation error

Change by R. David Murray : -- components: +Library (Lib) -email nosy: -barry, r.david.murray ___ Python tracker <https://bugs.python.org/issue35251> ___ ___

[issue35222] email.utils.formataddr is not exactly the reverse of email.utils.parseaddr

R. David Murray added the comment: Because the RFCs are defined only for ascii. Non-ascii in RFC 2822 addresses is an RFC violation. In python2 non-ascii would usually round-trip through these functions, but again that was an accident. If you'd like to propose a doc clarification

[issue35222] email.utils.formataddr is not exactly the reverse of email.utils.parseaddr

R. David Murray added the comment: Thanks for the report, but parseaddr and formataddr are defined *only* for ASCII. In the port to python3, parseaddr sort-of-maybe-sometimes does the naively expected thing with non-ascii, but that's just an accident. We could have added a check for non

[issue31242] Add SSLContext.set_verify_callback()

Change by David Peall : -- nosy: +David Peall ___ Python tracker <https://bugs.python.org/issue31242> ___ ___ Python-bugs-list mailing list Unsubscribe:

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

R. David Murray added the comment: The formatting of that doctest paragraph got messed up. Let me try again: >>> m = message_from_string("From: John Doe j...@example.com \n\n", policy=default) >>> m['From'].addresses (Address(display_name='', user

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

R. David Murray added the comment: >>> m = message_from_string("From: John Doe j...@example.com >>> \n\n", policy=default) >>> m['From'].addresses(Address(display_name='', username='John Doe jdoe', domain='example.com'),) The new policies have more

[issue35035] Documentation for email.utils is named email.util.rst

R. David Murray added the comment: Sure, this is fine with me. -- ___ Python tracker <https://bugs.python.org/issue35035> ___ ___ Python-bugs-list mailin

[issue34424] Unicode names break email header

R. David Murray added the comment: Michael, if you could check if Jens patch fixes your problem I would appreciate it. -- nosy: +michael.thies ___ Python tracker <https://bugs.python.org/issue34

[issue34424] Unicode names break email header

R. David Murray added the comment: I've requested some small changes on the PR. If Jens doesn't respond in another week or so someone else could pick it up. -- ___ Python tracker <https://bugs.python.org/issue34

[issue35057] Email header refolding adds additional \r in nested parse trees

R. David Murray added the comment: Thank you for the report. This is a duplicate of #34424, which has a PR. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue31522] _mboxMMDF.get_string() fails to pass param to get_bytes()

R. David Murray added the comment: New changeset d16f012f842e5719ff9fb90e217efc0f795853f2 by R. David Murray (Cheryl Sabella) in branch 'master': bpo-31522: mailbox.get_string: pass `from_` parameter to `get_bytes` (#9857) https://github.com/python/cpython/commit

[issue26441] email.charset: to_splittable and from_splittable are not there anymore!

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

[issue26441] email.charset: to_splittable and from_splittable are not there anymore!

R. David Murray added the comment: New changeset 5be00247ae0de2e24dd14bbe4d9ca159434a1710 by R. David Murray (Braden Groom) in branch 'master': bpo-26441: Remove documentation for deleted to_splittable and from_splittable methods (#9865) https://github.com/python/cpython/commit

[issue35016] \r to match add into address header with not-ascii character

R. David Murray added the comment: Thanks for the report and patch, but this is a duplicate of #34424. Your report prompted me to finally review the PR in that issue, though, so thanks twice :) -- resolution: -> duplicate stage: patch review -> resolved status: open -&g

[issue34954] Getting an email's subject is error-prone

R. David Murray added the comment: I'm guessing you got confused by the fact that the HTTP policy doesn't *add* new lines when *serializing*. If you can point to the part of the docs you read that produced that confusion, maybe we can improve

[issue34954] Getting an email's subject is error-prone

R. David Murray added the comment: Can you demonstrate that policy.default and policy.SMTP produce a subject with newlines? If they do, that is a serious bug. Please don't reopen the issue. I'll reopen it if you convince me there is a bug :) The statement you suggest we add

[issue34954] Getting an email's subject is error-prone

R. David Murray added the comment: The new policies *make* the email library that higher level library, that was pretty much the whole point :) I don't know how to make getting the fully decoded subject more intuitive than: msg['subject'] The fact that you have to specify a policy

[issue34954] Getting an email's subject is error-prone

R. David Murray added the comment: Use the new email policies in python3. It handles all the decoding for you. I'm afraid you are on your own for python2. -- resolution: -> out of date stage: -> resolved status: open -> closed _

[issue27321] Email parser creates a message object that can't be flattened

David Cannings added the comment: Ping on an ETA for this fix? -- nosy: +edeca ___ Python tracker <https://bugs.python.org/issue27321> ___ ___ Python-bugs-list m

[issue34881] unnecessary encoded-words usage breaks DKIM signatures

R. David Murray added the comment: You could also play with just making a parser that is a simplified version of get_unstructured, producing amaybe call it ASCIIOnlyUnstructuredTokenList...that would have as_ew_allowed set to False. That might not produce optimal results, but it would

[issue34881] unnecessary encoded-words usage breaks DKIM signatures

R. David Murray added the comment: See also issue 34277 for a previous discussion. I thought I had included a header-level toggle for encoded words, but that doesn't actually make sense, since by default a header value is treated as unstructured (which means encoded words are allowed

[issue21109] tarfile: Traversal attack vulnerability

Change by R. David Murray : -- nosy: -r.david.murray ___ Python tracker <https://bugs.python.org/issue21109> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34800] email.contentmanager raises error when policy.max_line_length==None or 0

R. David Murray added the comment: An unlimited line length would certainly satisfy the required minimum. As silane indicates, if max_line_length is 0 or None, the serializer is not supposed to wrap lines. (In fact one would like to have the option to control this separately

[issue34794] memory leak in TkApp:_createbytearray

David Talkin added the comment: Attached please find a Python script that demonstrates the bug. David On Tue, Sep 25, 2018 at 2:55 AM Karthikeyan Singaravelan < rep...@bugs.python.org> wrote: > > Karthikeyan Singaravelan added the comment: > > Thanks for the repor

[issue34794] memory leak in TkApp:_createbytearray

New submission from David Talkin : The Tkinter.PhotoImage class leaks memory with each change of the 'data' Attribute due to Image calling tk._createbytearray, which allocates memory, but never frees it. The offending method is in the TkApp class, _createbytearray(). -- components

[issue34776] Postponed annotations break inspection of dataclasses

New submission from David Hagen : The new postponed annotations have an unexpected interaction with dataclasses. Namely, you cannot get the type hints of any of the data classes methods. For example, I have some code that inspects the type parameters of a class's `__init__` method. (The real

[issue34660] Replace ableist terms and pejoratives in source code.

Change by R. David Murray : -- nosy: -r.david.murray ___ Python tracker <https://bugs.python.org/issue34660> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34660] Replace ableist terms and pejoratives in source code.

R. David Murray added the comment: > David and Brett: I consider part of the actions of the anonymous person using > the temporary aliases 25.45 and jonsees to be violations of our Code of > Conduct. I would therefore like you two to issue a warning, if not a ban. I am not i

[issue34694] Dismiss To Avoid Slave/Master wording cause it easier for non English spoken programmers

Change by R. David Murray : -- nosy: -r.david.murray ___ Python tracker <https://bugs.python.org/issue34694> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34659] Inconsistency between functools.reduce & itertools.accumulate

R. David Murray added the comment: Presumably because conceptually an 'initial value' would be like adding an additional element on to the front of the iterable being passed as an argument, and itertools is all about operating on iterables. I'm not saying such an argument could

[issue31652] make install fails: no module _ctypes

David Spahn added the comment: I'm getting the same error File "/usr/src/Python-3.7.0/Lib/ctypes/__init__.py", line 7, in from _ctypes import Union, Structure, Array ModuleNotFoundError: No module named '_ctypes' Makefile:1122: recipe for target 'install' failed make: **

[issue34601] Typo: "which would rather raise MemoryError than give up", than or then?

New submission from David Lin : https://docs.python.org/3/library/exceptions.html exception OverflowError Raised when the result of an arithmetic operation is too large to be represented. This cannot occur for integers (which would rather raise MemoryError than give up). However

[issue34582] VSTS builds should use new YAML syntax and pools

Change by David Staheli : -- nosy: David Staheli priority: normal severity: normal status: open title: VSTS builds should use new YAML syntax and pools ___ Python tracker <https://bugs.python.org/issue34

[issue34464] There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs

R. David Murray added the comment: I've removed 2.7 since those constants are not keywords in 2.7 (although None and __debug__ do raise syntax errors even in 2.7, they are not keywords there). Which is almost certainly why the docs treat them inconsistently (leftovers from before

[issue34438] do_handshake stuck in ssl.py

New submission from David : Sometimes, rarely, API calls will get stuck indefinitely on ssl.py. Stack trace: response = json.loads(urllib.request.urlopen(req).read()) File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen return opener.open(url, data, timeout)

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: check out https://devguide.python.org. (Basically, banch and generate a PR on github). And please open a new issue for this. -- ___ Python tracker <https://bugs.python.org/issue24

[issue24218] Also support SMTPUTF8 in smtplib's send_message method.

R. David Murray added the comment: Sorry, I haven't had time to look at it yet :( Not sure when I will, things are more than a bit busy for me right now. Ping me again in two weeks if I haven't responded, please. The proposed solution sounds reasonable, though, so you could also propose

[issue34357] situation where urllib3 works, but urllib does not work

David added the comment: martin.parter, it worked! Thanks so much, I was going nuts I also read the issue you pointed to, very interesting. Even if all servers should just work here, it does not seem to be the case in real life (I guess it's something easy to misconfigure) so I agree

[issue34357] situation where urllib3 works, but urllib does not work

David added the comment: Hi Martin. It's definitely something with my internet connection. Yesterday I temporarily changed the way I connect to the internet to use the mobile connection from my cell phone instead of my WiFi connection, and things started working. I also debugged

[issue34375] Subtests (unittest)

R. David Murray added the comment: https://docs.python.org/3/library/unittest.html#distinguishing-test-iterations-using-subtests -- nosy: +r.david.murray resolution: -> out of date stage: -> resolved status: open -> closed ___ Pytho

[issue34374] Shouldn't shutil.copyfile replace link in dst with follow_symlinks set?

R. David Murray added the comment: It is following the model of the posix cp command, whose equivalent to 'follow_symlinks' only affects the source. -- nosy: +r.david.murray ___ Python tracker <https://bugs.python.org/issue34

[issue34361] An error should be returned when there are spaces in between function name and parameters

R. David Murray added the comment: Sorry, but ignoring that whitespace is part of the python language definition. At this point in time, whatever the merits of the "beginner" argument, it is not going to change, for backward compatibility reasons if nothing else. -

[issue34357] situation where urllib3 works, but urllib does not work

New submission from David : Hello! Newbie to python here. I run into an issue with one desktop library, Cinnamon. Specifically this one: https://github.com/linuxmint/Cinnamon/issues/5926#issuecomment-411232144. This library uses the urllib in the standard library to download some json

[issue24255] Replace debuglevel-related logic with logging

R. David Murray added the comment: We generally do not fix "linting errors" unless they reveal logic errors or we touch the lines of code for some other reason. We also follow the existing style of a module rather than any particular style guide (the stdlib modules are often olde

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