Eric V. Smith added the comment:
I'm not sure what you're trying to accomplish here, but long and unichr are not
available in python 3.
2to3 has been deprecated and is no longer supported.
--
nosy: +eric.smith
___
Python tracker
<ht
Eric V. Smith added the comment:
Ah. longintrepr.h is an internal Python file, not meant for external
consumption. This file moved in Python 3.11. So this is still a yarl issue:
they'll need to adjust how they read that file. But my recommendation is that
they find another way to do what
Eric V. Smith added the comment:
It looks like you're missing dependencies required to compile yarl. Since this
isn't a bug with Python, I'm going to close this.
I suggest you ask the yarl community for help. Their home page is
https://github.com/aio-libs/yarl/
Good luck!
--
nosy
Change by Eric V. Smith :
--
resolution: -> not a bug
___
Python tracker
<https://bugs.python.org/issue46617>
___
___
Python-bugs-list mailing list
Unsubscrib
Eric V. Smith added the comment:
There's too much for us to look at here. Can you create a small example which
demonstrates the problem?
It should include the input, the code, the actual output, and the expected
output.
--
nosy: +eric.smith
Change by Eric V. Smith :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue46612>
___
___
Eric V. Smith added the comment:
The "evaluate the target" part causes the UnboundLocalError, just as in:
>>> x=1
>>> def f():
... x
... x = x + 1
...
>>> f()
Traceback (most recent call last):
File "", line 1, in
File "
Eric V. Smith added the comment:
The PR changes the meaning of assertCountEqual.
https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertCountEqual
says: Equivalent to: assertEqual(Counter(list(first)), Counter(list(second)))
...
At the very least, the documentation would
Eric V. Smith added the comment:
I'm going to close this issue. The behavior might be inconsistent with 2.7, but
I don't think that matters any more.
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracke
Eric V. Smith added the comment:
In case anyone cares: in a non-debug build, this error had no real effect. It
just caused the "find the literal part of an fstring" routine to terminate
early, but since the part that it had already identified was still in error, a
syntax error
Eric V. Smith added the comment:
Could you give an example of the problem?
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46557>
___
___
Eric V. Smith added the comment:
I was hoping to wait until the PEP 649 / PEP 563 thing was decided. But I
realize that no matter how that turns out, there will be a need to deal with
string annotations.
So I think I'm okay with the regex changes. Personally, I think we should
remove
Eric V. Smith added the comment:
dataclasses is no doubt too lenient. But it's just trying to accept valid
strings that look like ClassVar. Way back when this was initially implemented,
we decided that calling get_type_hints would be too expensive for every
dataclass, and would also
Eric V. Smith added the comment:
The dataclasses tests were in fact just added for completeness. I'd be okay
with changing dataclasses to reject leading spaces.
--
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
Thank you for the suggestion.
This is unlikely to gain acceptance. zip is usable in places outside of for
loops, whereas your suggestion appears to be only useful in for loops. In
addition, I don't see a way to specify the "strict" option using y
Eric V. Smith added the comment:
My thoughts are that I'd like PEP 563 to go away, and PEP 649 to be accepted,
and also never allow string literal annotations like the string
"Annotated[ClassVar[int]]". But since we'll no doubt have to support
string-ized annotations even
Change by Eric V. Smith :
--
nosy: -faizanjaved2021
title: Benefits Of Phool Makhana -> SPAM
___
Python tracker
<https://bugs.python.org/issue46515>
___
_
Change by Eric V. Smith :
--
Removed message: https://bugs.python.org/msg411578
___
Python tracker
<https://bugs.python.org/issue46515>
___
___
Python-bugs-list m
Change by Eric V. Smith :
--
pull_requests: +29064
pull_request: https://github.com/python/cpython/pull/30883
___
Python tracker
<https://bugs.python.org/issue46
Change by Eric V. Smith :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Eric V. Smith added the comment:
New changeset 894e8c13484822458d53cc77c9265b7a88450a4b by Miss Islington (bot)
in branch '3.10':
bpo-46503: Prevent an assert from firing when parsing some invalid \N sequences
in f-strings. (GH-30865) (GH-30866)
https://github.com/python/cpython/commit
Eric V. Smith added the comment:
New changeset c314e3e829943b186e1c894071f00c613433cfe5 by Miss Islington (bot)
in branch '3.9':
bpo-46503: Prevent an assert from firing when parsing some invalid \N sequences
in f-strings. (GH-30865) (30867)
https://github.com/python/cpython/commit
Eric V. Smith added the comment:
New changeset 0daf72194bd4e31de7f12020685bb39a14d6f45e by Eric V. Smith in
branch 'main':
bpo-46503: Prevent an assert from firing when parsing some invalid \N sequences
in f-strings. (GH-30865)
https://github.com/python/cpython/commit
Eric V. Smith added the comment:
Note that f'\N ' (with a single space) isn't enough to trigger this behavior.
It requires at least two characters after the '\N'. The first is when the
invalid string is recognized, and it's the presence of the second character
that triggers the failed
Change by Eric V. Smith :
--
keywords: +patch
pull_requests: +29046
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/30865
___
Python tracker
<https://bugs.python.org/issu
Eric V. Smith added the comment:
This triggers the same problem:
f'\N '
ast.literal_eval() isn't needed.
I think it's just the assert that's wrong, but I'm still checking.
--
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
I'll take a look.
--
___
Python tracker
<https://bugs.python.org/issue46503>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Eric V. Smith :
--
assignee: pablogsal -> eric.smith
___
Python tracker
<https://bugs.python.org/issue46503>
___
___
Python-bugs-list mailing list
Un
Change by Eric V. Smith :
--
type: crash -> behavior
___
Python tracker
<https://bugs.python.org/issue46499>
___
___
Python-bugs-list mailing list
Unsubscrib
Eric V. Smith added the comment:
Wow, thanks, Mark!
I'm generally in favor. The selling points to me are that it needs to happen
post-rounding, and the C++ discussion. It would be better if this were already
accepted in C++. I'll note that the paper is proposing a 'z' modifier to the
sign
Change by Eric V. Smith :
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46472>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Eric V. Smith :
--
status: open -> pending
___
Python tracker
<https://bugs.python.org/issue46461>
___
___
Python-bugs-list mailing list
Unsubscrib
Eric V. Smith added the comment:
Thanks, @yellowdusk1590!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Eric V. Smith added the comment:
New changeset 82c53229e18f5853c82cb8ab6b9af1925a0e9e58 by Yellow Dusk in branch
'main':
bpo-46442: improve and rename testExceptionCleanupNames (GH-30758)
https://github.com/python/cpython/commit/82c53229e18f5853c82cb8ab6b9af1925a0e9e58
Eric V. Smith added the comment:
Without a way to reproduce this, we won't be able to help you.
Ideally you would provide a python script, which we could run, which shows the
problem. It would be best if there were no third party packages involved, but
if there are, you should provide
Eric V. Smith added the comment:
Also see
https://docs.python.org/3/faq/programming.html#why-are-default-values-shared-between-objects
--
nosy: +eric.smith
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Pytho
Eric V. Smith added the comment:
I don't know for sure, but maybe it's trying to test "del" interacting with the
fact that the "as e" part doesn't escape the "except" clause, unlike normal
assignments:
>>> try:
... raise Exception
... except E
Eric V. Smith added the comment:
New changeset 0ae22577606f1b52e3b6c2de6c5b307518044605 by Erlend Egeberg
Aasland in branch '3.9':
[3.9] bpo-46402: Promote SQLite URI tricks in sqlite3 docs (GH-30660) (#30672)
https://github.com/python/cpython/commit/0ae22577606f1b52e3b6c2de6c5b307518044605
Eric V. Smith added the comment:
New changeset 01e6cbefd3d0f60c942ed711131f5d638dde1227 by Erlend Egeberg
Aasland in branch '3.10':
[3.10] bpo-46402: Promote SQLite URI tricks in sqlite3 docs (GH-30660)
(GH-30671)
https://github.com/python/cpython/commit
Eric V. Smith added the comment:
New changeset bdf2ab1887a2edfb089a3c2a1590cf1e84ea0048 by Erlend Egeberg
Aasland in branch 'main':
bpo-46402: Promote SQLite URI tricks in `sqlite3` docs (GH-30660)
https://github.com/python/cpython/commit/bdf2ab1887a2edfb089a3c2a1590cf1e84ea0048
Eric V. Smith added the comment:
It would also be interesting to see what attrs does in this case.
--
___
Python tracker
<https://bugs.python.org/issue46
Change by Eric V. Smith :
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46404>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric V. Smith added the comment:
I agree that would be a useful option.
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46402>
___
___
Eric V. Smith added the comment:
[And I was unable to add the numeric id as nosy. Apologies to the OP, who
probably will never see this! It's a bug in the bpo software.]
--
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
[Numeric id's automatically get dropped from the nosy list: trying to add it
back]
--
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
This is not the appropriate place to ask for help in debugging your code. I
suggest you ask on the python-list mailing list.
The error is that you're missing a bunch of right parenthesis in the isWinner()
function.
I do think "Syntax Error" isn'
Eric V. Smith added the comment:
In what way is it too strict? What "obsolete rules" are you referring to? What
are some example Message-Ids should be considered valid that instead get
truncated? What changes are you proposing?
--
nosy: +
Eric V. Smith added the comment:
I'll have to do some more research. But your analysis looks correct to me, so
far.
--
assignee: -> eric.smith
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issu
Eric V. Smith added the comment:
Can you show various paths, before and after your change? It’s not clear to me
what you’re proposing to change.
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46
Change by Eric V. Smith :
Removed file: https://bugs.python.org/file50558/Arlo camera setup.jpg
___
Python tracker
<https://bugs.python.org/issue46352>
___
___
Python-bug
Eric V. Smith added the comment:
I can't believe I missed that, Jason. I even read it twice!
I think this could go in pathlib, along with read_text. Maybe read_lines, or
iter_lines, or something. Of course PEP 533 is needed, too.
--
___
Python
Change by Eric V. Smith :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Eric V. Smith added the comment:
New changeset 0fc58c1e051026baff4919d8519ce2aabe3b2ba1 by Nikita Sobolev in
branch 'main':
bpo-46306: simplify `CodeType` attribute access in `doctest.py` (GH-30481)
https://github.com/python/cpython/commit/0fc58c1e051026baff4919d8519ce2aabe3b2ba1
Eric V. Smith added the comment:
Yes, the behavior is intentional. It might be relaxed in the future.
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
Thanks for committing this, @taleinat. But next time, if it's assigned to me,
I'd like to review it first. Thanks!
--
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
Hi, Jason.
How about:
>>> from pathlib import Path
>>> Path("foo.txt").read_text().splitlines()
['how', 'now', 'brown', 'cow']
Not the most elegant thing, I'll admit.
--
nosy: +eric.smith
__
Change by Eric V. Smith :
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46237>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Eric V. Smith :
--
assignee: docs@python -> eric.smith
___
Python tracker
<https://bugs.python.org/issue46290>
___
___
Python-bugs-list mai
Eric V. Smith added the comment:
Porting questions don't belong on the bug tracker. And we don't support 2.7 any
more, in any event.
You'll need to find python 3 versions of all of your packages. Unfortunately we
can't help you with that.
There used to be a python-porting mailing list
Eric V. Smith added the comment:
I don't want to belabor this, but hey, it's in f-strings! And if it's an actual
problem I'd like to fix it.
> It can be uninitialized if the parenstack[nested_depth] value is itself
> initialized, which can happen if the memory block pointed by pare
Eric V. Smith added the comment:
Thank you for posting this.
Some of these look like false positives.
For example:
#263
Parser/string_parser.c:670: error: Uninitialized Value
The value read from parenstack[_] was never initialized.
668. }
669. nested_depth
Eric V. Smith added the comment:
I see this has been reported in frida's tracker. It looks like a problem with
that package.
--
nosy: +eric.smith
type: crash -> behavior
___
Python tracker
<https://bugs.python.org/issu
Eric V. Smith added the comment:
No trouble. I'm glad to know it wasn't actually the same error as plain "foo)"
(although the error message is the same). That would have concerned me.
Changing the code so that it doesn't error out on the first problem it sees,
but kee
Eric V. Smith added the comment:
In fstring_find_expr, the code[0] that's checking for parens, braces, and
brackets detects the closing paren without a matching open paren.
The error message isn't incorrect: if you added a matching open paren the code
would compile:
>>> foo=lambd
Eric V. Smith added the comment:
Simpler reproducer:
>>> f"{foo)"
File "", line 1
f"{foo)"
^
SyntaxError: f-string: unmatched ')'
I assume this is the same error as:
>>> foo)
File "", line 1
foo)
^
Eric V. Smith added the comment:
Actually, the last line isn't necessary.
import logging.config
import json
log_config_txt = '''{
"version":1,
"formatters":{
"EXPLOIT":{
"class": "os.popen",
Eric V. Smith added the comment:
Thanks.
Here's a somewhat smaller, one-file version, that writes to the current
directory (I'm on Windows, no /tmp):
-
import logging
import logging.config
import json
log_config_txt = '''{
"version":1,
&
Eric V. Smith added the comment:
What are the contents of calculator.py?
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46251>
___
___
Eric V. Smith added the comment:
I think there's definitely room for improvement here, and at face value I like
the debugf() functions. __format__ style formatting solves a big problem for
me: being able to provide format strings for timestamps.
One thing: I'd be careful about saying
Change by Eric V. Smith :
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46200>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eric V. Smith added the comment:
This is likely not a bug in python. You might have better luck asking on a
numpy support list.
That said, what results do you get, and what do you expect to get? We don't
know what error you're seeing.
You might replace:
print("LB: ", LB)
wi
Eric V. Smith added the comment:
I think the documentation reads better as it currently is. Does this really
cause any practical confusion?
As Mark notes, we can't specify things exactly here: that would obfuscate all
of the things we're actually trying to say.
--
nosy: +eric.smith
Eric V. Smith added the comment:
@karzes: If you read all of the messages above, you'll find that the behavior
is deeply baked in to argparse. So, no, there is no fix for this issue.
I'm not sure about others, but I believe that the behavior is so deeply
ingrained in how argparse works
Eric V. Smith added the comment:
I think this is a rarely needed operation. I looked through a few tens of
thousand lines of my code and couldn't find anywhere it would be used.
Plus, you could write it yourself, so I don't see the advantage of it being
part of the language or standard
Eric V. Smith added the comment:
It looks like this was changed in https://bugs.python.org/issue42043
@jaraco might have some insights.
--
nosy: +jaraco
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
You're using a set (with {}), not a list (with []).
I'd give you a working example, but since you posted a picture I can't copy,
paste, and edit your example. In the future, please post text, not pictures.
--
nosy: +eric.smith
resolution
Eric V. Smith added the comment:
"type" is a natural name to use in this example, and isn't causing any
problems. I suggest not changing anything.
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.o
Eric V. Smith added the comment:
Please show the error you're getting, including the traceback.
--
status: pending -> open
___
Python tracker
<https://bugs.python.org/issu
Eric V. Smith added the comment:
In case it helps track this down. On my system I've tested these two setups:
On Windows, on the main branch, python just exists with no message when I run
this from the REPL.
Also on Windows, with the Cygwin 3.8.12 version, I get MemoryError:
Python 3.8.12
Eric V. Smith added the comment:
I know you know this, but here's a version without dataclasses, in case you
want to add a test for this, too.
from enum import Enum
class Foo:
def __init__(self, a):
self.a = a
def __repr__(self):
return f'Foo(a={self.a!r})'
class
Change by Eric V. Smith :
--
resolution: -> wont fix
___
Python tracker
<https://bugs.python.org/issue46081>
___
___
Python-bugs-list mailing list
Unsubscrib
Eric V. Smith added the comment:
problem_ary[:] creates a copy of problem_ary, so it's equal to:
>>> problem_ary[:]
[['a', 'b', 'c'], ['d', 'e', 'f'], ['g', 'h', 'i']]
The [1] element of that is:
>>> problem_ary[:][1]
['d', 'e', 'f']
So this is working as expected.
Eric V. Smith added the comment:
Good point, Serhiy. I also don't see how the proposed change is related to any
zip documentation (which is in the title of this issue).
I suggest closing this.
--
nosy: +eric.smith
___
Python tracker
<ht
Change by Eric V. Smith :
--
versions: -Python 3.6, Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issue46087>
___
___
Python-bugs-list m
Eric V. Smith added the comment:
Suggestions to improve it are welcomed. I can't think of a way to do it without
cluttering things up.
--
___
Python tracker
<https://bugs.python.org/issue46
Eric V. Smith added the comment:
The documentation at https://docs.python.org/3/library/unittest.html says "All
the assert methods accept a msg argument that, if specified, is used as the
error message on failure (see also longMessage). Note that the msg keyword
argument can be p
Change by Eric V. Smith :
--
nosy: +eric.smith, rhettinger, tim.peters
___
Python tracker
<https://bugs.python.org/issue46071>
___
___
Python-bugs-list mailin
Change by Eric V. Smith :
--
status: open -> pending
___
Python tracker
<https://bugs.python.org/issue46061>
___
___
Python-bugs-list mailing list
Unsubscrib
Eric V. Smith added the comment:
Please show the code that causes this problem. There’s not enough information
here to reproduce this failure.
--
nosy: +eric.smith
___
Python tracker
<https://bugs.python.org/issue46
Change by Eric V. Smith :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
title: Cannot use virtual environment on Windows 10 in cooperate security
settings -> Cannot use virtual environment on Windows 10 in corporate security
setti
Eric V. Smith added the comment:
@gianni: can you verify that your use case works in 3.11?
--
___
Python tracker
<https://bugs.python.org/issue44674>
___
___
Eric V. Smith added the comment:
Closing due to lack of feedback.
--
resolution: -> not a bug
stage: -> resolved
status: pending -> closed
___
Python tracker
<https://bugs.python.or
Change by Eric V. Smith :
--
resolution: -> out of date
stage: -> resolved
status: pending -> closed
___
Python tracker
<https://bugs.python.or
Eric V. Smith added the comment:
Closing due to lack of feedback.
--
resolution: -> not a bug
stage: -> resolved
status: pending -> closed
type: -> behavior
___
Python tracker
<https://bugs.python
Eric V. Smith added the comment:
Having not heard back about a use case for this, I'm going to close it. If you
want to move this forward, I suggest proposing it on the python-ideas mailing
list.
--
resolution: -> rejected
stage: -> resolved
status: pending -&g
Eric V. Smith added the comment:
Actually, printing out:
print(repr(path), repr(ZipPath(path)))
would be more useful.
If I don't hear back in a few days, I'm going to close this issue.
--
status: pending -> open
___
Python tracker
<
Change by Eric V. Smith :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Eric V. Smith added the comment:
New changeset e029c53e1a408b89a4e3edf30a9b38b094f9c880 by Eric V. Smith in
branch 'main':
bpo-44674: Use unhashability as a proxy for mutability for default dataclass
__init__ arguments. (GH-29867)
https://github.com/python/cpython/commit
Change by Eric V. Smith :
--
status: open -> pending
___
Python tracker
<https://bugs.python.org/issue46024>
___
___
Python-bugs-list mailing list
Unsubscrib
Eric V. Smith added the comment:
fromisoformat() is only designed to parse the output of isformat().
See issue 35829 for further discussion. I'm going to close this issue as a
duplicate.
--
nosy: +eric.smith
resolution: -> duplicate
stage: -> resolved
status: open -&g
101 - 200 of 2689 matches
Mail list logo