Barry A. Warsaw added the comment:
@sim0n - I added a comment to your open PR.
My main question for the rest of the group is whether we can and should
backport this. Given the new defect class being introduced, it seems like this
should only land in 3.10. Thoughts
Barry A. Warsaw added the comment:
Actually, it looks to me like the PR *does* include unittests, and I see them
in the repo, so I'm closing this bug.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
_
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue42115>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
@maggyero - I haven't merged PR 10016, but I left some additional comments.
Are you still interested in shepherding this PR?
--
___
Python tracker
<https://bugs.python.org/issue35
Barry A. Warsaw added the comment:
Apologies for the long delay in reviewing this bug. I'm looking at it now,
however since Python 3.7 is in security-only mode, this will only apply to
3.10, 3.9, and 3.8.
--
versions: +Python 3.10, Python 3.9 -Python 3.7
Barry A. Warsaw added the comment:
Actually, I think I am going to close this as won't fix, for two reasons.
First, this only potentially affects the legacy API, and second, in Python 3,
the error you get when you do it like the original repro example seems obvious
to me.
```
>&g
Barry A. Warsaw added the comment:
The other question is what to do about `EmailMessage` objects, which don't have
a `set_charset()` method. For now, I'll ignore that.
--
___
Python tracker
<https://bugs.python.org/issue1
Barry A. Warsaw added the comment:
I am seeing this in Brave (a Chrome derivative). Many examples in
https://docs.python.org/3/library/email.html
See the words "in\nterface" and "ob\nject' in the attached screenshot.
--
nosy: +barry
Added file: https://bugs.pytho
Barry A. Warsaw added the comment:
Updating the Python versions to the only active ones on which this bug could
conceivably be fixed. I haven't validated that it's still a problem, and I
haven't decided whether it's appropriate to backport to 3.9 and 3.8.
I'll work on a patch and see how
Change by Barry A. Warsaw :
--
assignee: -> barry
___
Python tracker
<https://bugs.python.org/issue1823>
___
___
Python-bugs-list mailing list
Unsubscrib
Barry A. Warsaw added the comment:
Thanks for the PR @iritkatriel but I'm inclined to close this as won't fix.
There are plenty of other changes someone would need to migrate to Python 3 for
the email package, so I think this is of limited benefit.
--
resolution: -> wont fix
st
Change by Barry A. Warsaw :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.10, Python 3.9 -Python 3.7
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
Thank you all for the fix. Closing.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
Thanks everyone for the fixes; I think this bug is now resolved. Closing.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
My understanding is that this is specifically a problem with the Objective-C
runtime that _scproxy.c accesses. The runtime is not thread safe and whereas
in earlier versions of macOS, it silently failed, now macOS is explicitly
aborting the process
New submission from Barry A. Warsaw :
This is very likely caused by something janky my ISP (AT) is doing with IPv6,
but the above named test fails for me because IPv6 addresses like `::1q` do not
fail to resolve as the test expects.
I'm not sure what can or should be done about
Change by Barry A. Warsaw :
--
keywords: +patch
nosy: +barry
nosy_count: 1.0 -> 2.0
pull_requests: +21740
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22775
___
Python tracker
<https://bugs.python.org/i
Change by Barry A. Warsaw :
--
versions: +Python 3.10
___
Python tracker
<https://bugs.python.org/issue37741>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I agree that we should close this issue, possibly with a documentation fix. I
wrote a blog posting about my investigations:
https://wefearchange.org/2018/11/forkmacos.rst.html
I don't think there's really much Python itself can do, and developers
Barry A. Warsaw added the comment:
Thanks for keeping the first 'F' in FLUFL! :D
--
___
Python tracker
<https://bugs.python.org/issue41251>
___
___
Python-bug
Barry A. Warsaw added the comment:
I don't think there's really anything more to do here. I'm closing the issue.
Let's open a new one if needed at some future point.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -&g
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue40453>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue39791>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
One simple restriction would be to disallow relative paths outside of the
resource anchor location.
--
___
Python tracker
<https://bugs.python.org/issue36
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38743>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38605>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
+1 Serhiy.
--
___
Python tracker
<https://bugs.python.org/issue38249>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw :
test_py_compile fails on macOS Catalina beta (19A573a)
==
ERROR: test_relative_path (test.test_py_compile.PyCompileTestsWithSourceEpoch
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38289>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38208>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
See also this ticket:
https://gitlab.com/python-devs/importlib_resources/issues/58
We've basically agreed that you should be able to load resources from
subdirectories that aren't packages. It turns out to be not a simple change in
importlib.resources
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38014>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue38010>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue34690>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I personally don't think we need to change this. C and Python are different,
and the PEP 7 rules have been in place for ages.
+Guido
--
nosy: +gvanrossum
___
Python tracker
<https://bugs.python.org/issue37
Barry A. Warsaw added the comment:
@jaraco will be able to answer that better than me. I actually thought those
did return concrete lists.
I also thought that the APIs accepted either a module or a package name, but
maybe I'm thinking about importlib.resources. Again, @jaraco can clarify
Barry A. Warsaw added the comment:
> OTOH This would require a PEP change, formal review, etc.
It would be trivial though. There are only two references to TargetScopeError
in the PEP. One talks about adding the exception and the other just mentions
it almost in passing as a subcl
Change by Barry A. Warsaw :
--
keywords: +patch
pull_requests: +14887
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/15153
___
Python tracker
<https://bugs.python.org/issu
Barry A. Warsaw added the comment:
I’ll do a PR for that too.
> On Aug 6, 2019, at 14:07, Brett Cannon wrote:
>
>
> Brett Cannon added the comment:
>
> If there's no porting benefit then let's move it to a single module inste
Barry A. Warsaw added the comment:
@jaraco - Why is the code in `Lib/importlib/metadata/__init__.py` instead of
`Lib/importlib/metadata.py`? Is that to make it easier to port between CPython
stdlib and the standalone version?
--
___
Python
Barry A. Warsaw added the comment:
There's an importlib.metadata.rst file which describes how to use the API, but
that doesn't appear to be linked from either the main library ToC or the
importlib documentation itself. I'll see if I can put together a PR to fix
this.
--
assignee
Barry A. Warsaw added the comment:
I know the PEP defines TargetScopeError as a subclass of SyntaxError, but it
doesn't really explain why a subclass is necessary. I think seeing
"TargetScopeError" will be a head scratcher. Why not just SyntaxError without
introducing a new
Barry A. Warsaw added the comment:
New changeset a4a994bd3e619cbaff97610a1cee8ffa87c672f5 by Barry Warsaw
(Abhilash Raj) in branch 'master':
bpo-37461: Fix infinite loop in parsing of specially crafted email headers
(GH-14794)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset f69d5c61981ea97d251db515c7ff280fcc17182d by Barry Warsaw (Paul
Ganssle) in branch 'master':
Fix infinite loop in email folding logic (GH-12732)
https://github.com/python/cpython/commit/f69d5c61981ea97d251db515c7ff280fcc17182d
Barry A. Warsaw added the comment:
I might be missing it, but I think the Language Reference still doesn't
document assignment expressions.
https://docs.python.org/3/reference/lexical_analysis.html#operators
There are likely other places in the LR that need to be filled out with PEP 572
Barry A. Warsaw added the comment:
New changeset 070d3d928d20ccb4790dd077f3794af3c2932e5c by Barry Warsaw (Miss
Islington (bot)) in branch '3.8':
bpo-37459: importlib docs improperly reference get_resource_loader() (GH-14568)
(GH-14580)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset d7d9c9f7c22113a405f1a340d050edfa2d024dff by Barry Warsaw (Miss
Islington (bot)) in branch '3.7':
bpo-37459: importlib docs improperly reference get_resource_loader() (GH-14568)
(GH-14581)
https://github.com/python/cpython/commit
Change by Barry A. Warsaw :
--
resolution: -> fixed
stage: patch review -> backport needed
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
New changeset b607d992e76e485f20be3bfd6b311525123f936b by Barry Warsaw
(aldwinaldwin) in branch 'master':
bpo-37459: importlib docs improperly reference get_resource_loader() (#14568)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
I still think the only way to read the documentation for parseaddr('a@b@c') is
to return ('', '') - a tuple of empty strings.
The documentations says:
"Returns a tuple of that information, unless the parse fails, in which case a
2-
Change by Barry A. Warsaw :
--
assignee: -> docs@python
components: +Documentation -Library (Lib)
nosy: +docs@python
___
Python tracker
<https://bugs.python.org/issu
Barry A. Warsaw added the comment:
Good catch. Are you going to submit a PR?
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue37459>
___
___
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue37449>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
New changeset b950cdb4beabeb093fa3ccc35f53d51cc0193aba by Barry Warsaw (Miss
Islington (bot)) in branch '3.7':
bpo-29412: Fix indexError when parsing a header value ending unexpectedly
(GH-14387) (GH-14412)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset 82654a037211a3466a294d53952926fc87f8403d by Barry Warsaw (Miss
Islington (bot)) in branch '3.8':
bpo-29412: Fix indexError when parsing a header value ending unexpectedly
(GH-14387) (GH-14411)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset 7213df7bbfd85378c6e42e1ac63144d5974bdcf6 by Barry Warsaw
(Abhilash Raj) in branch 'master':
bpo-29412: Fix indexError when parsing a header value ending unexpectedly
(GH-14387)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset 02257012f6d3821d816cb6a7e8461a88a05b9a08 by Barry Warsaw
(Abhilash Raj) in branch 'master':
bpo-33972: Fix EmailMessage.iter_attachments raising AttributeError. (GH-14119)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset f6713e84afc5addcfa8477dbdf2c027787f711c0 by Barry Warsaw
(websurfer5) in branch 'master':
bpo-36520: Email header folded incorrectly (#13608)
https://github.com/python/cpython/commit/f6713e84afc5addcfa8477dbdf2c027787f711c0
Barry A. Warsaw added the comment:
New changeset dc20fc4311dece19488299a7cd11317ffbe4d3c3 by Barry Warsaw (Miss
Islington (bot)) in branch '3.7':
bpo-21315: Fix parsing of encoded words with missing leading ws. (GH-13425)
(#13846)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset 66c4f3f38b867d8329b28c032bb907fd1a2f22d2 by Barry Warsaw
(Abhilash Raj) in branch 'master':
bpo-21315: Fix parsing of encoded words with missing leading ws. (#13425)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset aa79707262f893428665ef45b5e879129abca4aa by Barry Warsaw
(Abhilash Raj) in branch 'master':
bpo-30835: email: Fix AttributeError when parsing invalid CTE (GH-13598)
https://github.com/python/cpython/commit
Barry A. Warsaw added the comment:
New changeset 46d88a113142b26c01c95c93846a89318ba87ffc by Barry Warsaw
(Abhilash Raj) in branch 'master':
bpo-35805: Add parser for Message-ID email header. (GH-13397)
https://github.com/python/cpython/commit/46d88a113142b26c01c95c93846a89318ba87ffc
Barry A. Warsaw added the comment:
On Jun 4, 2019, at 08:11, STINNER Victor wrote:
> Ned Deily:
>> No, it has *always* been unsafe. What's new as of 10.13/14 is that macOS
>> tries much harder at runtime to detect such cases and more predictably cause
>> an error rather
Barry A. Warsaw added the comment:
On May 28, 2019, at 17:38, Ned Deily wrote:
>
> Ned Deily added the comment:
>
>> To be clear, what is unsafe on macOS (as of 10.13, but even more so on
>> 10.14) is calling into the Objective-C runtime between fork and exec.
&g
Barry A. Warsaw added the comment:
On May 28, 2019, at 17:21, STINNER Victor wrote:
>
>
> STINNER Victor added the comment:
>
>> To be clear, what is unsafe on macOS (as of 10.13, but even more so on
>> 10.14) is calling into the Objective-C runtime between fork an
Barry A. Warsaw added the comment:
On May 28, 2019, at 16:43, Ned Deily wrote:
> Thanks, I was just going to add that I would accept a doc change for 3.7.
> But the wording should be a little clearer that fork has *always* been unsafe
> on macOS, i.e. this is not a new issue for
Barry A. Warsaw added the comment:
On May 27, 2019, at 16:28, STINNER Victor wrote:
> I don't see a clear consensus to switch to spawn on *all* platforms, so I
> wrote PR 13603 which is the minimum fix: switch to spawn by default, but only
> on macOS.
Fair enough. Let’s fix wha
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue37044>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue37043>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
New changeset 1bbf7b661f0ac8aac12d5531928d9a85c98ec1a9 by Barry Warsaw (Jason
R. Coombs) in branch 'master':
bpo-34632: Add importlib.metadata (GH-12547)
https://github.com/python/cpython/commit/1bbf7b661f0ac8aac12d5531928d9a85c98ec1a9
Barry A. Warsaw added the comment:
Thanks @jaraco! This is now merged into 3.8.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
On May 10, 2019, at 04:07, Josh Rosenberg wrote:
>
> I've seen far too many cases where Python code targeting Linux intentionally
> uses the COW benefits of fork for multiprocessing to think it would be a good
> idea to change the default
Barry A. Warsaw added the comment:
One other suggestion: put the bulk of Tools/i18n/pygettext.py into
Lib/_pygettext.py, then import its main() in both Lib/gettext.py and
Tools/i18n/pygettext.py. Then just call that main().
--
nosy: +barry
Change by Barry A. Warsaw :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
New changeset b2758ff9553d8bebe4e9dd1cb3996212473810e3 by Barry Warsaw (Jason
R. Coombs) in branch 'master':
bpo-36832: add zipfile.Path (#13153)
https://github.com/python/cpython/commit/b2758ff9553d8bebe4e9dd1cb3996212473810e3
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue36820>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I'll assume you can resolve any weird corner cases, in which case +1
--
type: enhancement ->
___
Python tracker
<https://bugs.python.org/issu
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue36817>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On May 5, 2019, at 11:44, Davin Potts wrote:
>
> Victor raises an important question: should the *default* start behavior be
> made consistent across platforms?
Yes, I think it should. The pros of consistency and correctness outweigh the
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue36798>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Well, at least we're not alone. Here's a screen capture from Mail.app Version
12.4 (3445.104.8).
--
Added file: https://bugs.python.org/file48295/Screen Shot 2019-05-02 at
22.07.27.png
___
Python tracker
Barry A. Warsaw added the comment:
I've approved both PRs, however I am rather uncomfortable about the code
snippet in import.rst. Géry's change is a good one AFAICT, and thanks for the
contribution! I would feel much better about the long term correctness of this
code snippet if we had
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue14905>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue36740>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue36691>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
@veky - Thank you for pointing out splitlines(keepends=True). If we wanted
consistency, then we'd change the sense and use something like
.split(keepempty=True), however:
* I don't like run-on names, so I would suggest keep_empty
* Maybe just `keep
Barry A. Warsaw added the comment:
My sense is that we will never fix this, so closing as Won't Fix.
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Barry A. Warsaw added the comment:
On Mar 7, 2019, at 10:46, Ionel Cristian Mărieș wrote:
>
> There's a simple `if 'COVSOMETHING' in os.environ` check to activate it.
> That can't cost a significant amount of time. This is rather another bad
> actor argument.
You’re
Barry A. Warsaw added the comment:
On Mar 7, 2019, at 09:32, Anthony Sottile wrote:
>
>> I should have to start that package somehow.
>
> `pip install` is a pretty good opt-in already imo
Except that it conflates responsibilities. I may not want to opt into coverage
ev
Barry A. Warsaw added the comment:
On Mar 7, 2019, at 07:38, Steve Dower wrote:
>
> Steve Dower added the comment:
>
> There are two features here, let's be clear about what we're removing.
>
> * extending sys.path with static (perhaps relative) directories
> * arb
Barry A. Warsaw added the comment:
On Mar 6, 2019, at 19:04, Anthony Sottile wrote:
> It assigns `subprocess.run`, which is an api in python3.5+. In those
> versions, `subprocess.check_*` is implemented in terms of `subprocess.run`.
> The `subprocess.run` provided by that pa
Barry A. Warsaw added the comment:
+1
--
___
Python tracker
<https://bugs.python.org/issue35843>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Mar 1, 2019, at 19:59, Ivan Pozdeev wrote:
>
> Ivan Pozdeev added the comment:
>
> On 02.03.2019 2:25, Barry A. Warsaw wrote:
>> The fact that .pth files are global and affect the entire Python
>> installation. <...> Righ
Barry A. Warsaw added the comment:
On Mar 1, 2019, at 09:27, Ivan Pozdeev wrote:
> Startup code (custom or not) is not a dependency of anything. It rather
> customizes the environment in which the program specified by the user would
> run, _before_ any user code could be allow
Barry A. Warsaw added the comment:
On Feb 28, 2019, at 09:40, Anthony Sottile wrote:
>
> I don't think even this is unanimous. Things like registering codecs,
> instrumenting coverage in subprocesses, etc. all seem like legitimate uses of
> the arbitrary code execution feature
Barry A. Warsaw added the comment:
On Feb 26, 2019, at 13:05, Gregory Szorc wrote:
>
> I would think the two would agree about whether a path with separators is a
> resource or not. The documentation at
> https://docs.python.org/3.7/library/importlib.html#importlib.abc.Re
Barry A. Warsaw added the comment:
On Feb 26, 2019, at 13:23, Ivan Pozdeev wrote:
>
> Easy. Insert a chunk into site.py that would call pdb.set_trace() if an
> envvar (e.g. `PYSITEDEBUG') or a command line switch is set.
>
> Actually, why can't whoever has this problem a
Barry A. Warsaw added the comment:
On Feb 26, 2019, at 12:52, Ionel Cristian Mărieș wrote:
>
> Something bad was installed with sudo but suddenly sudo is not acceptable for
> debugging? This seems crazy.
Your sudo may not be my sudo. :) Let’s say I update my Ubuntu desktop a
Barry A. Warsaw added the comment:
On Feb 26, 2019, at 12:32, Steve Dower wrote:
>
> There are 100 other ways to end up in this situation though. Why is *this*
> one so much worse?
Because there’s no good place to stick a pdb/breakpoint to debug such issues
other tha
Barry A. Warsaw added the comment:
On Feb 26, 2019, at 05:19, Nick Coghlan wrote:
>
> I just don't want to lose the "add this location to sys.path" behaviour that
> exists for lines in pth files that *don't* start with "import ", since that
> has plenty of le
101 - 200 of 2236 matches
Mail list logo