Logan Jones added the comment:
Ok I now have a PR up with the features requested. Let me know if you need
anything else!
--
___
Python tracker
<https://bugs.python.org/issue44
Change by Logan Jones :
--
pull_requests: +30264
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/32187
___
Python tracker
<https://bugs.python.org/issu
Logan Jones added the comment:
Okay, I'm actually able to work on this again. What is the best way to make
this change real. Should I be working off of main?
--
___
Python tracker
<https://bugs.python.org/is
Logan Jones added the comment:
Based on my reading I’m hopeful that this change can make it in quickly once I
find the time. The previous implementation didn’t care how the processes were
created.
I will look as soon as I can
--
___
Python
Logan Jones added the comment:
Hi Bozhi. The syntax that you're referencing was added in 3.9. So if you're
trying the syntax in earlier versions of Python, it won't work. The standard
collections were added in PEP 585 (https://www.python.org/dev/peps/pep-0585/)
I think
Change by Logan Jones :
--
nosy: +loganasherjones
___
Python tracker
<https://bugs.python.org/issue44920>
___
___
Python-bugs-list mailing list
Unsubscribe:
Logan Jones added the comment:
If I've understood what you've written correctly, what you want is to change
urlparse to use the WHATWG URL Standard (https://url.spec.whatwg.org/).
I'm not a committer or anything, but that seems like a large API change and is
not likely to ha
Logan Jones added the comment:
I don't know if urlparse is actually "mishandling" these URLs.
Looking over RFC 1808 (https://datatracker.ietf.org/doc/html/rfc1808.html) the
BNF (https://datatracker.ietf.org/doc/html/rfc1808.html#section-2.2) seems to
support what urlparse i
Change by Logan Jones :
--
nosy: +loganasherjones
___
Python tracker
<https://bugs.python.org/issue44744>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Logan Jones :
--
keywords: +patch
pull_requests: +25911
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27373
___
Python tracker
<https://bugs.python.org/issu
Logan Jones added the comment:
I think I have a solution for this, but I'm pretty new to contributing. Still
writing up some tests.
--
___
Python tracker
<https://bugs.python.org/is
Change by Logan Jones :
--
nosy: +loganasherjones
___
Python tracker
<https://bugs.python.org/issue44733>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Logan Jones :
--
keywords: +patch
nosy: +loganasherjones
nosy_count: 1.0 -> 2.0
pull_requests: +25885
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27343
___
Python tracker
<https://bugs.p
Logan Jones added the comment:
After speaking with Lukasz about this, it seems like the unparser is using the
normal unicode repr to determine what should be returned. The default unicode
repr will escape quotes if necessary. This is not allowed for f-strings and is
the root cause of the
Logan Jones added the comment:
I'm working on this in the PyCon 2019 sprints.
Near as I can tell, while this issue still seems relevant, I think it might
actually be for the best that this multiple disambiguation is left in the test
suite.
I removed the pid reference in the TESTFN an
Logan Jones added the comment:
I'd like to work on this during the Pycon sprints
--
nosy: +loganasherjones
___
Python tracker
<https://bugs.python.org/is
Change by Logan Jones :
--
keywords: +patch
pull_requests: +13021
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Logan Jones added the comment:
I'm going to try to tackle this. I'm not exactly sure how to go about updating
the PEP, but the docs should have a PR in the next 15 minutes or so.
--
nosy: +Logan Jones
___
Python tracker
<https://bu
18 matches
Mail list logo