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:
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 mo
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:
> 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 subclass
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 cl
Barry A. Warsaw added the comment:
I'm not sure it would be any better, but what about defining something like a
DateFormatDefect and returning that?
--
___
Python tracker
<http://bugs.python.org/is
Barry A. Warsaw added the comment:
Thanks for all the great detailed background, and the suggested approaches. I
think there are a couple of constraints that would be good to resolve.
* parsedate_to_datetime() is documented as "performing the same function as
parsedate()" with a
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue30429>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I agree with everything @serhiy.storchaka said, including the questionable
utility of the l* methods in Python 3. ;)
Thanks also for updating the documentation. Reading the existing docs over
now, it's shocking how imprecise "the translation is r
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue29593>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
It's probably fine, since it should be a rare occurrence, but it of course has
the potential to break things like tests (doc and otherwise). Unlikely, but it
should be pointed out. Still, I'm also fine with backporting it.
--
no
New submission from Barry A. Warsaw:
The devguide does touch on how to build Python from source using homebrew
installed libraries on macOS, although I found it to be 1) a bit incomplete; 2)
not so easy to discover.
It might make sense to modify configure to autodetect homebrew, or to have a
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue31280>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue30761>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
There is a very minor opportunity for NULL dereference in compile.c.
compiler_subdict() does not check the return value of get_const_value(), which
could be NULL. This was found by Kirit Sankar Gupta.
This is not a security issue in practice, since
Barry A. Warsaw added the comment:
As it's barely worth fixing, it's not worth backporting.
--
___
Python tracker
<http://bugs.python.org/issue31337>
___
___
Changes by Barry A. Warsaw :
--
pull_requests: +3325
___
Python tracker
<http://bugs.python.org/issue31337>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I'll preface that it's not a major issue that I feel *has* to be fixed, but
given that assert *can* be compiled away, does it make sense to use abort()
instead? E.g.
1 file changed, 2 insertions(+), 2 deletions(-)
Python/compile.c | 4 ++--
Changes by Barry A. Warsaw :
--
versions: +Python 3.7 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue1198569>
___
___
Python-bugs-list mailin
Barry A. Warsaw added the comment:
Sorry for the long delay. It looks like Ian's original link is no longer
valid. Do you have an updated link to a possible doctest or example?
--
___
Python tracker
<http://bugs.python.org/issu
Barry A. Warsaw added the comment:
On Sep 4, 2017, at 10:18, Serhiy Storchaka wrote:
> Serhiy Storchaka added the comment:
>
> Could you please also look at other asserts? I have counted 48 occurrences of
> assert(0), 11 assert(0 && "message") and 2
Changes by Barry A. Warsaw :
--
pull_requests: +3326
___
Python tracker
<http://bugs.python.org/issue1198569>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
Over in bpo-31337 the observation was made that we often use the following
pattern in situations we never expect to hit:
assert(0);
return NULL;
but this isn't strictly optimal. First, the asserts can be compiled away.
Second, it's possibl
Barry A. Warsaw added the comment:
See bpo-31338 for adopting the abort() idiom.
--
___
Python tracker
<http://bugs.python.org/issue31337>
___
___
Python-bug
Barry A. Warsaw added the comment:
Never mind; I crafted a decent test for the PR.
--
___
Python tracker
<http://bugs.python.org/issue1198569>
___
___
Python-bug
Barry A. Warsaw added the comment:
New changeset ba4279683f8eb8f59be10d12547ea89480614388 by Barry Warsaw in
branch 'master':
bpo-1198569: Allow string.Template braced pattern to be different (#3288)
https://github.com/python/cpython/commit/ba4279683f8eb8f59be10d12547ea8
Changes by Barry A. Warsaw :
--
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Changes by Barry A. Warsaw :
--
pull_requests: +3334
___
Python tracker
<http://bugs.python.org/issue1198569>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
New changeset 973b901212bd84d279904bab6654709f4ec32470 by Barry Warsaw in
branch 'master':
What's New for bpo-1198569 (#3303)
https://github.com/python/cpython/commit/973b901212bd84d279904bab6
Barry A. Warsaw added the comment:
I'm thinking there are two aspects to this. One would involve updates to PEP 7
to include a section on "Unreachable code". The other would be a PR that
updates the current C code to the PEP 7 standard.
I'll work on a PEP update as a
Barry A. Warsaw added the comment:
@skrah - quick question. Is /* NOT REACHED */ a common convention? Do any
compilers or IDEs recognize it? Is it documented anywhere? I like the idea of
adding that comment on the abort(), but I'm trying to find some prior art or
references for
Barry A. Warsaw added the comment:
>
> Can we have a Py_UNREACHABLE() macro for that, then?
> First, it makes the intent extra clear without needing any additional
> comment. Second, it can be defined however we need in order to get along
> with the various to
Changes by Barry A. Warsaw :
--
pull_requests: +3358
___
Python tracker
<http://bugs.python.org/issue31338>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Barry A. Warsaw:
Placeholder issue for discussion of the design of the implementation of PEP 553.
--
assignee: barry
components: Interpreter Core
messages: 301372
nosy: barry
priority: normal
severity: normal
status: open
title: Implement PEP 553 - built-in debug
Changes by Barry A. Warsaw :
--
pull_requests: +3370
___
Python tracker
<http://bugs.python.org/issue31353>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
So with this diff:
modified Include/pymacro.h
@@ -95,4 +95,6 @@
#define Py_UNUSED(name) _unused_ ## name
#endif
+#define Py_UNREACHABLE() abort()
+
#endif /* Py_PYMACRO_H */
modified Python/compile.c
@@ -1350,8 +1350,7 @@ get_const_value(expr_ty e
Barry A. Warsaw added the comment:
On Sep 5, 2017, at 16:07, STINNER Victor wrote:
>
> STINNER Victor added the comment:
>
>> Neither gcc (macOS, Ubuntu), nor clang (Ubuntu) complain.
>
> Ok, cool. In that case, go ahead.
I checked with @steve.dower and I think abort()
Barry A. Warsaw added the comment:
Alright, I'm going to close this bug in favor of bpo-31338
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.pyth
Changes by Barry A. Warsaw :
--
pull_requests: +3385
___
Python tracker
<http://bugs.python.org/issue31338>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
So, while we do have a conflict between consistency and utility, I think
@r.david.murry 's last comment has convinced me that raising the exception is
more helpful. I think we should do that, fixing the documentation and giving
up on the consistency
New submission from Barry A. Warsaw:
IPython has a neat little feature where the function that enters the debugger
takes an optional `header` argument. If given, it is a string that's printed
to the console just before the debugger is entered.
https://github.com/ipython/ipython/blob/m
Barry A. Warsaw added the comment:
And specifically `header` is chosen to match IPython. Why be different?
--
___
Python tracker
<https://bugs.python.org/issue31
Changes by Barry A. Warsaw :
--
keywords: +patch
pull_requests: +3435
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue31389>
___
___
Py
New submission from Barry A. Warsaw:
Placeholder issue for discussion of the design of the implementation of PEP 559.
--
assignee: barry
components: Interpreter Core
messages: 301816
nosy: barry
priority: normal
severity: normal
status: open
title: Implement PEP 559 - built-in noop
Changes by Barry A. Warsaw :
--
keywords: +patch
pull_requests: +3470
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue31409>
___
___
Py
Barry A. Warsaw added the comment:
Rejected by GvR!
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
Barry A. Warsaw added the comment:
New changeset b2e5794870eb4728ddfaafc0f79a40299576434f by Barry Warsaw in
branch 'master':
bpo-31338 (#3374)
https://github.com/python/cpython/commit/b2e5794870eb4728ddfaafc0f79a40299576434f
--
___
Pyth
Changes by Barry A. Warsaw :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue31338>
___
___
Barry A. Warsaw added the comment:
New changeset 35425d638c0eeb8377620e016f47df3ae08d7061 by Barry Warsaw in
branch 'master':
bpo-31389 Add an optional `header` argument to pdb.set_trace() (#3438)
https://github.com/python/cpython/commit/35425d638c0eeb8377620e016f47df
Changes by Barry A. Warsaw :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue31558>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I'm actually fine either way. Consider me a solid ±0
--
___
Python tracker
<https://bugs.python.org/issue34850>
___
___
Barry A. Warsaw added the comment:
I think it make sense to disable this test; the only possible modification
would be to only disable it for macOS <= 10.13. AFAIK, that's the first
version where core dumps were possible. (Aside: I also saw these core dumps
for a long time on 1
Barry A. Warsaw added the comment:
On Dec 12, 2018, at 17:59, Ned Deily wrote:
>
> Ned Deily added the comment:
>
>> Would it be safe to run the multiprocessing tests on recent macOS with the
>> OBJC_DISABLE_INITIALIZE_FORK_SAFETY environment variable set?
>
>
Barry A. Warsaw added the comment:
Let's extend the "joke" and make it mandatory in Python 4! :)
--
___
Python tracker
<https://bugs.pyt
Barry A. Warsaw added the comment:
New changeset 55cc34500e5abbfedb89adc95e3f94d53c544933 by Barry Warsaw (Chris
Rands) in branch 'master':
bpo-35526: make __future__.barry_as_FLUFL mandatory for Python 4.0 (#11218)
https://github.com/python/cpyt
Change by Barry A. Warsaw :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue35651>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue35673>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On the first point, I'd categorize this as a documentation bug, and in fact,
it's inconsistent with the language reference, which doesn't have the same
language:
https://docs.python.org/3/reference/import.html#__loader__
On the second poi
Change by Barry A. Warsaw :
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue35673>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
On Jan 7, 2019, at 03:16, Ronald Oussoren wrote:
>
> Do you know why the namespace package loader lies about the source and code?
> Both .get_source() and .get_code() return a value that isn't None.
> And likewise: Why is the namespace
Barry A. Warsaw added the comment:
> To make a potentially viable concrete proposal here, I think a reasonable
> first step would be to change the ".pth" file processing code in site.py to
> emit PendingDeprecationWarning for the 'if line.startswith(("impor
Barry A. Warsaw added the comment:
On Jan 14, 2019, at 04:02, STINNER Victor wrote:
>
> I really hate .pth files because the slow down Python startup time for *all*
> applications whereas .pth files are usually specific to a very few
> applications using one or two spec
Barry A. Warsaw added the comment:
On Jan 14, 2019, at 04:14, Antoine Pitrou wrote:
>
> As I said: editable installs (`pip install -e`) are an important use case of
> .pth files.
Is that true outside of virtual environments? I care less about .pth files
inside venvs, since
Barry A. Warsaw added the comment:
On Jan 14, 2019, at 07:17, Nick Coghlan wrote:
>
> I'll also reiterate that I am *completely* opposed to deprecating the "append
> entries to sys.path" usage model, as there is absolutely nothing wrong with
> that (if distros a
Barry A. Warsaw added the comment:
On Jan 14, 2019, at 17:30, STINNER Victor wrote:
>
> I don't think that you will like it, but I feel that a PEP will be needed
> here to list use cases and explain what replace .pth files for each use
> case. Maybe no replacement for some
Barry A. Warsaw added the comment:
I believe this bug does not affect Python 3.8:
(Using a Python 3.8 virtualenv):
% python demo.pyz
Reading: resource.txt
Length: 19
% python `pwd`/demo.pyz
Reading: resource.txt
Length: 19
I think it's too risky (and too much work, given it would ha
Change by Barry A. Warsaw :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue35321>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Frozen module's origin isn't really documented AFAICT. Here's the link to the
library reference:
https://docs.python.org/3/library/importlib.html?highlight=origin#importlib.machinery.ModuleSpec.origin
The language reference doesn't rea
Barry A. Warsaw added the comment:
I am mentoring Nina so I'll review this.
--
___
Python tracker
<https://bugs.python.org/issue35321>
___
___
Python-bugs-l
Barry A. Warsaw added the comment:
Yes, it should be deprecated and removed. TBH, IMHO smtpd.py should be
entirely deprecated. aiosmtpd (3rd party) is a much more modern approach.
--
___
Python tracker
<https://bugs.python.org/issue35
Barry A. Warsaw added the comment:
On Jan 22, 2019, at 07:16, Samuel Colvin wrote:
>
> Ok, if I create a PR, should it just remove MailmanProxy completely or mark
> it as deprecated in the docs to be removed in 3.9?
>
> Personally, I think it should be ok to remove it comp
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue35835>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
versions: +Python 3.6
___
Python tracker
<https://bugs.python.org/issue35321>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue35839>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
New changeset 69091cb497b2f0fe7e2789b30b43cf78caf9de9b by Barry Warsaw (Nina
Zakharenko) in branch 'master':
bpo-35321: Set the spec origin to frozen in frozen modules (#11732)
https://github.com/python/cpyt
Change by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<https://bugs.python.org/issue35905>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
All I know is that for 3.7 and 3.8 (3.6 is different), I have this little
helper script to build against Homebrew libraries.
#!/bin/sh
export CPPFLAGS="-I$(brew --prefix sqlite3)/include -I$(brew --prefix
zlib)/include"
export LDFLAGS="-L
Barry A. Warsaw added the comment:
Nosying myself since I just landed here based on an internal $work bug report.
We're seeing it with reads. I'll try to set aside some work time to review the
PRs.
--
nosy: +barry
___
Python track
Change by Barry A. Warsaw :
--
title: open().write() fails on 2 GB+ data (OS X) -> open().write() and .read()
fails on 2 GB+ data (OS X)
___
Python tracker
<https://bugs.python.org/issu
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue29708>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Shouldn't this at least also cover Python 3.7? And should it be officially
backported? I would think that if https://github.com/python/cpython/pull/296
gets accepted for 3.7, then distros that care can cherry pick it back into
whatever versions they
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue29729>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
bools are subclasses of int and False and True have integer equivalents:
https://docs.python.org/3/library/stdtypes.html#bltin-boolean-values
--
nosy: +barry
resolution: -> not a bug
stage: -> resolved
status: open -&g
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue29779>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
I don't think the Python envar has to follow the contraction from bash.
$PYTHONHISTORY reads very nicely.
I have similar code in my $PYTHONSTARTUP, but it would be nice to be able to
get rid of it and just let Python do the common
Barry A. Warsaw added the comment:
On Mar 12, 2017, at 11:42 AM, Chi Hsuan Yen wrote:
>That's a great feature! Here's a question: what should be CPython's behavior
>when PYTHONHISTORY is explicitly set to empty? Currently there's an error:
>
>$ PYTHONH
Barry A. Warsaw added the comment:
I was going to say that this is an API change, but given that without this,
folks would have to catch both exceptions and now only have to catch one of
them, it isn't.
--
nosy: +barry
___
Python tracker
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue14208>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
As bytes?
--
___
Python tracker
<http://bugs.python.org/issue29857>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Barry A. Warsaw :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue29857>
___
___
Python-bugs-list mailing list
Unsubscribe:
Barry A. Warsaw added the comment:
Is EHLO the only command sent in lower case? I think it might not be.
I suppose I'm a solid ±0 on changing this (how's that for a completely neutral
endorsement?). I won't do the change myself, but I'd r
Barry A. Warsaw added the comment:
On Mar 21, 2017, at 11:47 AM, STINNER Victor wrote:
>No, text please. Text is just more convenient in Python, and it's trivial to
>retrieve original bytes:
>
>raw_args_bytes = [os.fsencode(arg) for arg in sys._raw_args]
Well, "raw args&
Barry A. Warsaw added the comment:
New changeset 0a1b656d8ce3da14f8acf947477b8e998e68ef3b by Barry Warsaw in
branch '3.6':
bpo-25008: Deprecate smtpd and point to aiosmtpd (#274) (#278)
https://github.com/python/cpython/commit/0a1b656d8ce3da14f8acf947477b8e
Barry A. Warsaw added the comment:
New changeset 66b5092fac4264efdc9c508a7dd425fa9833e147 by Barry Warsaw in
branch '3.5':
bpo-25008: Deprecate smtpd and point to aiosmtpd (#274) (#279)
https://github.com/python/cpython/commit/66b5092fac4264efdc9c508a7dd425
Barry A. Warsaw added the comment:
New changeset f37b0cb230069481609b0bb06891b5dd26320504 by Barry Warsaw in
branch '3.4':
bpo-25008: Deprecate smtpd and point to aiosmtpd (#274) (#280)
https://github.com/python/cpython/commit/f37b0cb230069481609b0bb06891b5
Barry A. Warsaw added the comment:
New changeset 1bc156430bad8177b5beecf57979628c1d071230 by Barry Warsaw
(Matthias Bussonnier) in branch 'master':
bpo-29546: Improve from-import error message with location (#103)
https://github.com/python/cpyt
Barry A. Warsaw added the comment:
We should really restructure string.Template documentation to emphasize i18n.
That's always been its prime use case, and f-strings don't change that (because
f-strings are not really appropriate for translations). Before f-strings,
string.Te
Changes by Barry A. Warsaw :
--
assignee: docs@python -> barry
___
Python tracker
<http://bugs.python.org/issue19824>
___
___
Python-bugs-list mailing list
Un
901 - 1000 of 2273 matches
Mail list logo