[issue28633] Concatenating bytes literal and f-string causes segmentation fault
Eric V. Smith added the comment: It's a decref of a NULL pointer. Patch with test is attached. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file45383/28633-0.diff ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28633> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28385] Bytes objects should reject all formatting codes with an error message
Eric V. Smith added the comment: LGTM, although I'm not so sure about your #3. Maybe it should be a separate issue and raised on python-dev? But I don't feel strongly enough about it to argue the point. Thanks! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28385> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28489] Fix comment in tokenizer.c
Eric V. Smith added the comment: FWIW, in Lib/tokenize.py, it's _all_string_prefixes(): >>> _all_string_prefixes() set(['', 'FR', 'rB', 'rF', 'BR', 'Fr', 'RF', 'rf', 'RB', 'fr', 'B', 'rb', 'F', 'Br', 'R', 'U', 'br', 'fR', 'b', 'f', 'Rb', 'Rf', 'r', 'u', 'bR']) My basic point is that trying to list them all is hard and a maintenance problem. So as long as we're not being exhaustive, the comment should just state the gist of what the code does. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28489> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28489] Fix comment in tokenizer.c
Eric V. Smith added the comment: That's great. Thanks! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28489> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28489] Fix comment in tokenizer.c
Changes by Eric V. Smith <e...@trueblade.com>: -- stage: -> commit review ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28489> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28489] Fix comment in tokenizer.c
Eric V. Smith added the comment: I'd actually change this to be something like: Process b"", r"", u"", and the various legal combinations. There are 24 total combinations when you add upper case. I actually wrote a script in Lib/tokenize.py to generate them all. And when I add binary f-strings, that number climbs to 80. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28489> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28673] When using pyro4 with more than 15 threads, python 2.7.12 cores frequently
Eric V. Smith added the comment: Can you provide a short sample that causes this error? Without a way to reproduce it, there's not a lot we can do. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28673> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10379] locale.format() input regression
Changes by Eric V. Smith <e...@trueblade.com>: -- versions: +Python 3.5, Python 3.6 -Python 3.3, Python 3.4 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10379> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10379] locale.format() input regression
Changes by Eric V. Smith <e...@trueblade.com>: -- assignee: docs@python -> keywords: +easy stage: -> needs patch type: -> behavior ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10379> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28827] f-strings: format spec should not accept unicode escapes
Eric V. Smith added the comment:
I think this is documented. This is a result of supported nested expressions in
the format_spec:
>>> an_x = "X"
>>> f'{10:02{an_x}}'
'0A'
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28827>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28827] f-strings: format spec should not accept unicode escapes
Eric V. Smith added the comment:
Specifically, see: https://www.python.org/dev/peps/pep-0498/#format-specifiers
str.format() also works this way:
>>> '{0:02{1}}'.format(10, an_x)
'0A'
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28827>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28757] Installation Failure
Eric V. Smith added the comment: Thanks for the bug report. However, 3.2 is no longer supported. If you can reproduce this with 3.5 or 3.6, then please list the exact steps, including: OS version where you got the file you downloaded what steps you took to install it I'm closing this, but feel free to re-open it if you can reproduce with a supported version of Python. -- nosy: +eric.smith resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28757> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28739] PEP 498: docstrings as f-strings
Eric V. Smith added the comment: As you've seen, the answer is "no"! We'd need to add logic to evaluate them at function definition time. That would be a slight noticeable change, if the expressions had side effects. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28739> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28739] PEP 498: docstrings as f-strings
Eric V. Smith added the comment: It's Ned's call, but I wouldn't recommend changing this in 3.6, at least not 3.6.0. As Martin points out, the reason f'foo' is a "normal" string has to do with how strings and f-strings are assembled and concatenated. Similarly: 'foo' f'bar' 'baz' is a normal string, 'foobarbaz'. I can't think of another place that requires a "normal" string, but if they exist, they'd be affected by this, too. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28739> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28745] Python 3.5.2 "from ... import" statement is different from official documentation
Changes by Eric V. Smith <e...@trueblade.com>: -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28745> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28741] PEP 498: single '}' is not allowed
Eric V. Smith added the comment: Thanks. Fixed in the pep repo in 4e86033. -- assignee: docs@python -> eric.smith resolution: -> fixed status: open -> closed type: -> enhancement ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28741> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: Here's an updated patch, that fixes some problems with the earlier patch, and adds equivalent support for bytes. HOWEVER, I can't get the warnings machinery to raise a DeprecationWarning that would have all of the equivalent information that an actual SyntaxError would have. So this patch still raises SyntaxError, but with a better error context. I'm going to keep plugging away at this, but I'm hoping that someone with more experience with warnings using the C-API can chime in with some advice. Given the tight deadline, I can use all of the help I can get. The two functions that need help are decode_bytes_with_escapes and decode_unicode_with_escapes in ast.c. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Changes by Eric V. Smith <e...@trueblade.com>: -- stage: needs patch -> patch review ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Changes by Eric V. Smith <e...@trueblade.com>: Added file: http://bugs.python.org/file45284/28128-2.diff ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28385] Bytes objects should reject all formatting codes with an error message
Eric V. Smith added the comment: I would change the f-string tests. I realize it's a fragile test, but it's the only way to test the strings in the exception. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28385> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: Oops, use 28128-3.diff. -- Added file: http://bugs.python.org/file45285/28128-3.diff ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28385] Bytes objects should reject all formatting codes with an error message
Eric V. Smith added the comment: I don't have a strong feeling one way or the other. I'd be surprised if anyone is catching these errors. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28385> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: I'll take a look at it, Emanuel. But I can't promise how much progress I'll be able to make today. I also think that at that point it becomes so complex that it fails Ned's test for inclusion in 3.6. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: I've pushed this to the default branch. I'll watch the buildbots. Then Ned can decide if this goes in to 3.6. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment:
Serihy:
I had tried this approach earlier, but it doesn't work. With your -5.diff
patch, the output is (using Nick's test case):
$ rm -rf __pycache__/ ; ./python -Werror escape_warning.py
Traceback (most recent call last):
File "escape_warning.py", line 1, in
import bad_escape
DeprecationWarning: invalid escape sequence \d
$
With my -4.diff patch, you get the desired full stack trace:
$ rm -rf __pycache__/ ; ./python -Wall escape_warning.py
Traceback (most recent call last):
File "escape_warning.py", line 1, in
import bad_escape
File "/home/eric/local/python/cpython/bad_escape.py", line 1
print('\d')
^
SyntaxError: invalid escape sequence \d
$
The trick is: how to make the DeprecationWarning version produce output similar
to the SyntaxError case? Note that with DeprecationWarning, you don't see the
line in bad_escape.py that actually contains the string with the invalid escape.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28128>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: I'm not in front of a computer at the moment, but the output looks good. Also, my very quick glance at -7.diff's warn_invalid_escape_sequence looks reasonable, although I can't say for sure whether raising the error in PyErr_WarnExplicitObject followed by raising another error in ast_error is absolutely correct (it's outside my expertise). -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: Also, you'll note that with or without your patch, you get the same behavior. The code in hg already raises DeprecationWarning, just in a different place. So unless we can improve the DeprecationWarning output, we're better off doing nothing. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28385] Bytes objects should reject all formatting codes with an error message
Eric V. Smith added the comment: TypeError is documented as "Raised when an operation or function is applied to an object of inappropriate type". I think that fits this case: you're applying some format code to a type that doesn't support it. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28385> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: I agree it would be nice to get this in to 3.6. I'm not sure I'd go so far as to say it's a must and can't wait for 3.6.1. It's a non-trivial change, and it's up to Ned to say if it can go in to 3.6. If you don't run with -Wall or -Werror, then you won't notice any new behavior with invalid escapes, correct? Maybe post to python-dev and see if we can get more reviewers? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: I'll work on this as soon as I can, coordinating with Ned. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: I'll work on this later today. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28597] f-string behavior is conflicting with its documentation
Eric V. Smith added the comment:
This is a duplicate of issue 28590.
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> fstring's '{' from escape sequences does not start an expression
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28597>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28582] Invalid backslash syntax errors are not always accurate as to the location on the line where the error occurs
Changes by Eric V. Smith <e...@trueblade.com>: -- stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28582> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28590] fstring's '{' from escape sequences does not start an expression
Eric V. Smith added the comment: I'm currently working on an update to PEP-498 to address this. I hope to have it completed after a sprint this weekend. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28590> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Changes by Eric V. Smith <e...@trueblade.com>: -- assignee: -> eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28128] Improve the warning message for invalid escape sequences
Eric V. Smith added the comment: Chi Hsuan Yen: I'll investigate, and open another issue as needed. -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28582] Invalid backslash syntax errors are not always accurate as to the location on the line where the error occurs
New submission from Eric V. Smith: See msg279799 from issue28128, repeated here: Seems the ^ pointer is not always correct. For example, in the function scope it's correct: $ cat test.py def foo(): s = 'C:\Program Files\Microsoft' $ python3.7 -W error test.py File "test.py", line 2 s = 'C:\Program Files\Microsoft' ^ SyntaxError: invalid escape sequence \P On the other hand, top-level literals confuses the pointer: $ cat test.py s = 'C:\Program Files\Microsoft' $ python3.7 -W error test.py File "test.py", line 1 s = 'C:\Program Files\Microsoft' ^ SyntaxError: invalid escape sequence \P Is that expected? -- components: Interpreter Core messages: 279888 nosy: Chi Hsuan Yen, eric.smith priority: normal severity: normal status: open title: Invalid backslash syntax errors are not always accurate as to the location on the line where the error occurs type: behavior versions: Python 3.6, Python 3.7 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28582> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28424] pkgutil.get_data() doesn't work with namespace packages
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28424> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28425] Python3 ignores __init__.py that are links to /dev/null
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28425> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28433] Add sorted (ordered) containers
Eric V. Smith added the comment: I'm sure this has been discussed before and rejected. I suggest you search the python-ideas mailing list archives, and if you do not find something in the archives, raise the issue on python-ideas. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28433> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28804] file tell() report incorrect file position on Windows (but Linux is OK)
Eric V. Smith added the comment: Yes, it's a duplicate. The only valid operation on the value of calling tell() from a text-mode file is to pass it to seek(). As long as that works, there's no bug here. -- nosy: +eric.smith resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> io.TextIOWrapper.tell() report 65bit number when mix readline() + tell() ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28804> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28975] os.walk generator giving inconsistent results
Eric V. Smith added the comment:
Assuming Path is pathlib.Path, this is equivalent to the difference between:
>>> list(os.walk('/tmp'))
[('/tmp',
and:
>>> list(os.walk('/tmp/'))
[('/tmp/',
Because:
>>> pathlib.Path('/tmp')
PosixPath('/tmp')
>>> pathlib.Path('/tmp/')
PosixPath('/tmp')
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28975>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28975] os.walk generator giving inconsistent results
Eric V. Smith added the comment: Isn't the difference that you use os.walk(Path(source)) in the first example, and os.walk(source) in the second one? -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28975> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28739] PEP 498: docstrings as f-strings
Eric V. Smith added the comment: It looks good to me, save for one tiny issue. I left a review comment. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28739> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28838] Uniformize argument names of "call" functions (C API)
Eric V. Smith added the comment: I withdraw my concern. I was thinking it would affect the caller, but of course it won't. Apologies. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28838> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28841] urlparse.urlparse() parses invalid URI without generating an error (examples provided)
Eric V. Smith added the comment: And note that there are tests that explicitly check that the colon with no port works (via issue 20270). Given that this behavior has been around for a while, and is explicitly allowed, I would recommend against changing this to an error. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28841> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28838] Uniformize argument names of "call" functions (C API)
Eric V. Smith added the comment: Isn't this just a lot of churn for not a lot of benefit? I'm all for consistency, but you'll break patches on the bug tracker and externally maintained patches. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28838> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28841] urlparse.urlparse() parses invalid URI without generating an error (examples provided)
Eric V. Smith added the comment: Can you please paste your code into a comment on this issue? Gist content has a habit of vanishing. Thanks! -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28841> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29144] Implicit namespace packages in Python 3.6
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29144> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29164] make test always fail at 218/405 ( AssertionError: ', ' not found in '1234.5' )
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29164> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment:
This problem was no doubt introduced after 3.6a1 when I changed the parsing to
disallow backslashes inside {}.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29104>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment:
Yes:
>>> f'\{2*5}'
'\\{10'
I agree '\\10' would make sense.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29104>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment: Do you have a link to the SO question? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29104> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment:
I'm not sure this counts as an error. The backslash means to treat the next
character literally, which this does. And since \{ is not a valid escape
sequence, it keeps both characters, exactly like:
>>> '\c'
'\\c'
Furthermore, since unknown escape sequences are deprecated, this usage is going
to be an error in the future. You can see this now with -Werror:
$ python.exe -Werror
Python 3.6.0b1+ (3.6:87de1f12c41c+, Sep 16 2016, 07:05:57) [MSC v.1900 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> f'\{10}'
DeprecationWarning: invalid escape sequence '\{'
>>> '\c'
DeprecationWarning: invalid escape sequence '\c'
>>>
Since this works as I expect it to now, and since it will become an error in
the future, I don't think any change is warranted.
--
assignee: -> eric.smith
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29104>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment: But I admit that dropping the trailing } seems odd. I think this particular usage should be an error: no bare } allowed, similar to: >>> f'10}' File "", line 1 SyntaxError: f-string: single '}' is not allowed -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29104> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28975] os.walk generator giving inconsistent results
Changes by Eric V. Smith <e...@trueblade.com>: -- stage: -> resolved ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28975> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29047] Where are the test results stored?
Eric V. Smith added the comment: https://github.com/python/devguide/blob/github/runtests.rst -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29047> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29890] Constructor of ipaddress.IPv*Interface does not follow documentation
Eric V. Smith added the comment: This should be easy enough to fix, at least in IPv4Interface.__init__. It needs to copy some of IPv4Network.__init__, dealing with address[1] and calling _make_netmask(). Currently, it just calls int(address[1]). I haven't looked at IPv6Interface. Tests are also needed, of course. -- keywords: +easy nosy: +eric.smith stage: -> needs patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29890> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29890] Constructor of ipaddress.IPv*Interface does not follow documentation
Eric V. Smith added the comment: While an IPv4Interface may be a subclass of an IPv4Address, it definitely has more information attached to it: the netmask of the network it's on. So an interface (like a network) needs to allow additional parameters to specify the netmask. It should be true that IPv4Interface is like IPv4Network, but it will allow arbitrary host bits. A IPv4Network in strict mode will have all zeros for the host bits, while a IPv4Network in non-strict mode will allow ones in the host bits (see Ilya's original example). If you look at IPv4Interface.__init__, it actually does just that: creates an IPv4Network with strict=False, then extracts the network parts. I'm not exactly sure why it also has the int(address[1]) code there, too, since IPvv4Network deals with the address[1] part. I would think extracting _prefixlen from the network (as it does later in __init__ for the non-tuple case) would be good enough. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29890> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29890] Constructor of ipaddress.IPv*Interface does not follow documentation
Eric V. Smith added the comment: Thanks! Yes, we'll need tests. I'm out of town most of the weekend, but I'll look at this as soon as I can. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29890> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29947] In SocketServer, why not passing a factory instance for the RequestHandlerClass instead of the class itself?
Eric V. Smith added the comment: Just a guess, but it's because this code was written at a time when subclassing was the preferred way to extend code. Now we know better :), but it's not possible to change history, unfortunately. Lots of code depends on the current behavior. If you find a way to make a factory function work, while preserving backward comparability, then we can re-open this issue and consider the enhancement request then. -- nosy: +eric.smith resolution: -> rejected stage: -> resolved status: open -> closed versions: -Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29947> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29837] python3 pycopg2 import issue on solaris 10
Eric V. Smith added the comment: This would be an issue for pscyopg2 support, not the Python bug tracker. You're probably using an unsupported combination of psycopg2 and postgres libraries. -- nosy: +eric.smith resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29837> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29863] Add a COMPACT constant to the json module
Eric V. Smith added the comment: +1: gets the job done without complicating the API. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29863> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29805] Pathlib.replace cannot move file to a different drive on Windows if filename different
Eric V. Smith added the comment: I agree this needs to be different from replace(), due to not being atomic. That makes it an enhancement, so I'm removing 3.5. I'm +1 on Path supporting something like shutil.move(). -- nosy: +eric.smith type: -> enhancement versions: -Python 3.5 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29805> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment: Serhiy: I plan to find time in the next week or so to look at this. Sorry for the delay. Plus, the new workflow isn't helping me out: I need to get up to speed on it. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29104> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30031] Improve queens demo (use argparse and singular form)
Eric V. Smith added the comment: I think these are reasonable improvements. Also, move the initialization of "silent" in to __new__. -- keywords: +easy nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30031> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30023] Example code becomes invalid for "Why do lambdas defined in a loop with different values all return the same result?"
Eric V. Smith added the comment: That's consistent with the example: it's showing you how to create a list of functions, that when called, return squares. "This gives you a list that contains 5 lambdas that calculate x**2" Maybe "squares" isn't the most awesome name, but I think if you read the example in its entirety, it's all consistent and correct. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30023> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30023] Example code becomes invalid for "Why do lambdas defined in a loop with different values all return the same result?"
Changes by Eric V. Smith <e...@trueblade.com>: -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30023> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30031] Improve queens demo (use argparse and singular form)
Eric V. Smith added the comment: Oops, yes, __init__. Plenty of the demos use imports. I think it would be clearer with argparse, but I also don't feel strongly about it. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30031> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29965] MatchObject __getitem__() should support slicing and len
Eric V. Smith added the comment: Short of a compelling use case, I suggest we reject this enhancement request. len() was deliberately not added in #24454. It's not like any normal code would be iterating over match groups. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29965> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30090] Failed to build these modules: _ctypes
Changes by Eric V. Smith <e...@trueblade.com>: -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30090> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30104] clang 4.0 miscompiles dtoa.c, giving broken float parsing and printing
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30104> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30127] argparse action not correctly describing the right behavior
Eric V. Smith added the comment: I think the example is correct. Because baz's action is store_false, the default is True. So if baz is omitted, it should have a True value. That's what the example shows, and what I see when I run this code. Can you show what you tested, what you saw, and what you expected? -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30127> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30124] Fix C aliasing issue in Python/dtoa.c to use strict aliasing on Clang 4.0
Eric V. Smith added the comment: I agree we shouldn't do anything heroic to "fix" dtoa.c. I'd wait and see if Gay (or other maintainers) will chose an approach if Clang keeps this behavior. At most, I think Mark's idea to use -fno-strict-aliasing only on dtoa.c and nowhere else would be the better approach. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30124> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29777] argparse arguments in main parser hide an argument in subparser
Eric V. Smith added the comment: No, we won't be adding new features to 2.7. Sorry. -- nosy: +eric.smith resolution: -> rejected stage: -> resolved type: -> enhancement ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29777> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29771] An email and MIME handling package - Add support to send CC of email
Eric V. Smith added the comment: The examples don't cover it, but look at the documentation for setting arbitrary mail headers such as CC. And look at smtplib.SMTP.sendmail() on sending a message to arbitrary recipients (to, cc, or bcc are all the same): https://docs.python.org/2/library/smtplib.html#smtplib.SMTP.sendmail -- nosy: +eric.smith resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29771> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29771] An email and MIME handling package - Add support to send CC of email
Eric V. Smith added the comment: You need to review how SMTP works. The contents of the mail message have no bearing on where messages are sent. That's exactly how BCC works: there's nothing in the message telling you who is BCC'd, but the mail is still sent to the BCC recipients, via SMTP. Similarly, you could have the message say that some...@example.com is in the To: header, but not send it to them via SMTP. I'm on the fence about including this in the examples. In any event, this bug tracker is not a place for an email tutorial. From your SO link, there's a reference (by user xyref) to another question which explains this in detail: http://stackoverflow.com/questions/1546367/python-how-to-send-mail-with-to-cc-and-bcc. This completely explains the issue. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29771> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29771] An email and MIME handling package - Add support to send CC of email
Eric V. Smith added the comment: So, you want to improve the examples? I wouldn't be opposed to that. I don't see that there's any code to change. -- assignee: -> docs@python components: +Documentation nosy: +docs@python ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29771> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29777] argparse arguments in main parser hide an argument in subparser
Changes by Eric V. Smith <e...@trueblade.com>: -- resolution: rejected -> stage: resolved -> needs patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29777> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28739] PEP 498: docstrings as f-strings
Eric V. Smith added the comment: Yes, I think it can be closed. Thanks! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28739> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29696] Use namedtuple in string.Formatter.parse iterator response
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith title: Use namedtuple in Formatter.parse iterator response -> Use namedtuple in string.Formatter.parse iterator response ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29696> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29696] Use namedtuple in string.Formatter.parse iterator response
Eric V. Smith added the comment: It's in string.py, so it would be easy just to add a namedtuple there: class Formatter: ... def parse(self, format_string): return _string.formatter_parser(format_string) I don't see a need to add a structseq to _string, since it's a private API. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29696> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29696] Use namedtuple in string.Formatter.parse iterator response
Changes by Eric V. Smith <e...@trueblade.com>: -- versions: +Python 3.7 -Python 3.5 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29696> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29708] support reproducible Python builds
Eric V. Smith added the comment: -- Eric. > On Mar 3, 2017, at 6:36 AM, Bernhard M. Wiedemann <rep...@bugs.python.org> > wrote: > > > New submission from Bernhard M. Wiedemann: > > See https://reproducible-builds.org/ and > https://reproducible-builds.org/docs/buy-in/ for why this is a good thing to > have in general. > > Fedora, openSUSE and possibly other Linux distributions package .pyc files as > part of their binary rpm packages and they are not trivial to drop [1]. > > A .pyc header includes the timestamp of the source .py file > which creates non-reproducible builds when the .py file is touched during > build time (e.g. for a version.py). > As of 2017-02-10 in openSUSE Factory this affected 476 packages (such as > python-amqp and python3-Twisted). > > > [1] http://lists.opensuse.org/opensuse-packaging/2017-02/msg00086.html > > -- > components: Build, Distutils > messages: 20 > nosy: bmwiedemann, dstufft, merwok > priority: normal > pull_requests: 353 > severity: normal > status: open > title: support reproducible Python builds > versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 > > ___ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue29708> > ___ > ___ > New-bugs-announce mailing list > new-bugs-annou...@python.org > https://mail.python.org/mailman/listinfo/new-bugs-announce > -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29708> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30906] os.path.join misjoins paths
Eric V. Smith added the comment: We absolutely cannot change this to give an error if the second or subsequent parameters is absolute. I have code that reads user-named config files. If the path is relative, it's relative to a config directory, but it's allowed to be absolute: config_filename = os.path.join(config_dir, user_supplied_name) -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30906> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30978] str.format_map() silences exceptions in __getitem__
Eric V. Smith added the comment: I'm -0 on a backport. The new behavior is more correct, but I don't like changing the exception type in a micro release. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30978> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30978] str.format_map() silences exceptions in __getitem__
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30978> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30793] Parsing error on f-string-expressions containing strings with backslash
Eric V. Smith added the comment:
The reason that this was done was to give us flexibility in deciding how the
backslashes should be interpreted in the future. I announced it on python-dev
here: https://mail.python.org/pipermail/python-dev/2016-August/145979.html.
That message contains a link to the python-ideas discussion that precipitated
the change.
PEP 536 is one proposal to change how this is handled. I don't entirely agree
with it, since I think allowing:
f'Magic wand: { bag['wand'] }'
would be confusing and make life more difficult for simple (regex based)
parsers to skip over f-strings.
Notice that in Jupiter
(https://github.com/jupyter/notebook/issues/2037#issuecomment-272466046) and in
CodeMirror
(https://github.com/codemirror/CodeMirror/commit/c45674b11e990fe37abc662b0c507d3bb1f635e7#diff-04f7f1f1bbbab888742c7e849187a79c)
they were able to make simple changes to their parsers and "support" f-strings
(for some value of "support": mostly not break in the presence of f-strings).
However, I'm not completely opposed to revisiting the issue. Your use case is
certainly a compelling one.
--
assignee: -> eric.smith
nosy: +eric.smith
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30793>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30124] Fix C aliasing issue in Python/dtoa.c to use strict aliasing on Clang 4.0
Eric V. Smith added the comment: > Unfortunately, as far as I know, clang still does not support > function-level optimization pragmas. Maybe it was implemented > recently, but then you would still have to have a workaround> > for older versions. I realize the answer is probably "no", but I'll ask anyway. Do you know if they support whole-module optimization pragmas? That would still be better than mucking with makefiles to get a per-module flag. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30124> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31136] raw strings cannot end with a backslash character r'\'
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31136> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31140] Insufficient error message with incorrect formated string literal
Eric V. Smith added the comment: Thanks. There was some work on this recently: I'll try and check 3.7 later today. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31140> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31140] Insufficient error message with incorrect formated string literal
Eric V. Smith added the comment: On 3.6.1 on Windows, I get: % python3 bpo-31140.py File "", line 1 (a>2s) ^ SyntaxError: invalid syntax Which is far from ideal, but at least points to (a portion of) the correct text. I won't have access to a copy of 3.6.2 or 3.7 until later today. Can you show the exact output from 3.6.2? -- components: +Interpreter Core nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31140> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31232] Backport the new custom "print >> sys.stderr" error message?
Eric V. Smith added the comment: I'm in favor of backporting to 3.6. It's not an intrusive change and is helpful in porting 2.x scripts. -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31232> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29104] Left bracket remains in format string result when '\' preceeds it
Eric V. Smith added the comment: This is on my list of things to review at PyCon, when I should finally have some free time. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29104> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28974] Make default __format__ be equivalent to __str__
Eric V. Smith added the comment: I'm okay with this change. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28974> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30426] why not use the same style func name. eg: int.to_bytes (with underline) and array.tobytes(without underline).
Eric V. Smith added the comment: We won't do that, because then we'd have two functions that do the same thing. There's no sense having to learn two functions, just to achieve consistency. Sorry. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30426> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30426] why not use the same style func name. eg: int.to_bytes (with underline) and array.tobytes(without underline).
Eric V. Smith added the comment: There's no particular reason, we just weren't careful about enforcing a consistent style, especially on older code. But whatever the reason, it's now too late to change this. -- nosy: +eric.smith resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30426> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30590] str.format no longer accepts unpacked defaultdict for default values
Changes by Eric V. Smith <e...@trueblade.com>: -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30590> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30597] Show expected input in custom "print" error message
Eric V. Smith added the comment: You'll need to be careful about fully translating to python 3, though. What do you do with: print >> sys.stderr, "message" or: print "message", ? -- nosy: +eric.smith ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30597> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30529] Incorrect error messages for invalid whitespaces in f-string subexpressions
Eric V. Smith added the comment: Sorry, I've been busy. I'll get to this soon, though. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30529> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
