date:20200511

[issue40591] \r broken in IDLE

2020-05-11 Thread wyz23x2



New submission from wyz23x2 :

When you run this code:

import time
for i in range(10):
print(f"\r{i}", end='', flush=True)
time.sleep(1)
print('\n')

On CMD it prints 0 at the first time, then it will erase it and print the 
increased i. But on IDLE it just prints "0123456789" -- that isn't right.

--
assignee: terry.reedy
components: IDLE
messages: 368616
nosy: terry.reedy, wyz23x2
priority: normal
severity: normal
status: open
title: \r broken in IDLE
type: behavior
versions: Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue29587] Generator/coroutine 'throw' discards exc_info state, which is bad

2020-05-11 Thread Chris Jerdonek



Chris Jerdonek  added the comment:

Would someone be able to approve / take a look at this small PR addressing 
another aspect of this issue?
https://github.com/python/cpython/pull/19858
I'm hoping it can be part of 3.9, and the deadline is just a week away.

It builds on the already merged PR to address an "Example 3" of this issue (the 
"yield from" case as opposed to the "yield" case, which the merged PR 
addressed):

Example 3:

def f():
yield

def g():
try:
raise KeyError('a')
except Exception:
yield from f()

gen = g()
gen.send(None)
gen.throw(ValueError)

--
Output without PR:

Traceback (most recent call last):
  File "/.../test-example3.py", line 12, in 
gen.throw(ValueError)
  File "/.../test-example3.py", line 8, in g
yield from f()
  File "/.../test-example3.py", line 2, in f
yield
ValueError

--
Output with PR:

Traceback (most recent call last):
  File "/.../test-example3.py", line 6, in g
raise KeyError('a')
KeyError: 'a'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/.../test-example3.py", line 12, in 
gen.throw(ValueError)
  File "/.../test-example3.py", line 8, in g
yield from f()
  File "/.../test-example3.py", line 2, in f
yield
ValueError

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40257] Improve the use of doc in pydoc

2020-05-11 Thread Serhiy Storchaka



Serhiy Storchaka  added the comment:

help(1) as well as help(int) output the help for int. The only difference is 
that the former has the first line "Help on int object:", and the latter -- 
"Help on class int in module builtins:".

If IPython wants to output the help on the instance, it should change the 
implementation of `?` and `??`. It would be better if it correctly attribute 
the source of the docstring: the object itself, its class or its superclass. It 
was difficult to distinguish these cases before, now it is easier.

By the way, I just tried IPython 5.5.0 with Python 3.6.9, and it does not 
output the docstring either:

In [1]: a = 1

In [2]: a??
Type:int
String form: 1

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40503] PEP 615: Add zoneinfo module

2020-05-11 Thread Thomas Wouters



Thomas Wouters  added the comment:

The normal way to do this (for make/autoconf) is to add a --with-tzpath 
argument to configure.ac, and a make variable to pass it to the compilation of 
anything that needs it. You can then access it from Python code with 
sysconfig.get_config_var().

In configure.ac, AC_SUBST(TZPATH) makes configure replace @TZPATH@ in the 
Makefile with the value you set to $TZPATH in configure.ac.  You then either 
add that to the global PY_CFLAGS_NODIST, or modify the build rule for the 
module that needs it to pass it along. (See for example how 
GITTAG/GITVERSION/GITBRANCH are passed to Modules/getbuildinfo.o.)

AC_ARG_WITH() is how you add a new --with-* argument to configure. The usual 
way people do this is by copying one of the other AC_ARG_WITH blocks and 
modifying it to suit their needs. It's a mixture of m4 and shell that can be a 
bit annoying to get right, but it's pretty flexible. Run autoreconf to 
regenerate configure. You can manually check that the shell in configure makes 
sense.

Something will have to be done on the Windows side as well, but I'm not sure 
what. Adding Steve Dower for that.

--
nosy: +steve.dower

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40592] `Shutil.which` incosistent with windows's `where`

2020-05-11 Thread Dawid Gosławski


New submission from Dawid Gosławski :

Shutil's which implementation does not work correctly when someone set's empty 
item in `PATHEXT` environment variable. Example:

set PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.RB;.RBW;

I'm not 100% sure how I got this in my PATHEXT config, I wasn't changing that 
so maybe some bugged uninstaller not removed it's extension correctly.

This makes things confusing as Windows will find correctly binary, but Python 
will return nothing, due to this part:

```
if any(cmd.lower().endswith(ext.lower()) for ext in pathext):
files = [cmd]
```

pathext is initialized as `pathext = os.environ.get("PATHEXT", 
"").split(os.pathsep)`, which ends producing '' as last element

Because any string ends with empty string (''), files list will have plain 
version added like `git`, which will then fail executable check.

Workaround is to use full name `git.exe`

Filtering out empty strings would fix that.

--
components: Library (Lib)
messages: 368620
nosy: alkuzad
priority: normal
severity: normal
status: open
title: `Shutil.which` incosistent with windows's `where`

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40584] PyType_FromModuleAndSpec function should add the process of tp_vectorcall_offset

2020-05-11 Thread Petr Viktorin



Petr Viktorin  added the comment:

That seems reasonable. See the discussion around 
https://bugs.python.org/issue38140 for context.

Note that __dictoffset__ and __weaklistoffset__ are also exposed as members (in 
PyMemberDef type_members) and documented (Doc/c-api/structures.rst). A new 
__vectorcalloffset__ should have that as well.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40592] `Shutil.which` incosistent with windows's `where`

2020-05-11 Thread Serhiy Storchaka



Change by Serhiy Storchaka :


--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40593] Improve error reporting for invalid character in source code

2020-05-11 Thread Serhiy Storchaka

New submission from Serhiy Storchaka :

Currently you get SyntaxError with message "invalid character in identifier" in
two cases:

1. The source code contains some non-ASCII non-identifier character. Usually it
happens when you copy code from internet page or PDF file which was "improved"
by some enhachaizer which replaces spaces with non-breacking spaces, ASCII
minus with a dash or Unicode minus, ASCII quotes with fancy Unicode quotes.
They do not look like a part of identifier at all. The error message also does
not say what character is invalid, and it is hard to find the culprit because
they look too similar to correct characters (especially with some monospace
fonts).

See
https://mail.python.org/archives/list/python-id...@python.org/thread/ILMNJ46EAL4ENYK7LLDLGIMYQKZAMMWU/
for discussion.

2. Other case is very special -- when the source code contains the declaration
for the utf-8 encoding followed by non-UTF-8 bytes sequences. It is rarely
happen in real world.

The proposed PR improves errors for these cases.

>>> print(123—45)
File "", line 1
print(123—45)
^
SyntaxError: invalid character '—' (U+2014)

* The error message no longer contains misleading "in identifier".

* The error message contains the invalid character, literal and its hexcode.

* The caret points on the invalid character. Previously it pointed on the last
non-ascii or non-alphabetical character followed the invalid character (5 in
the above example).

* For the special case of non-decodable UTF-8 sequence the syntax error message
is more informative: "(unicode error) 'utf-8' codec can't decode byte 0xff
...". Although this case needs further improvements.

--
components: Interpreter Core
messages: 368622
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: Improve error reporting for invalid character in source code
type: enhancement
versions: Python 3.9

___
Python tracker

___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40593] Improve error reporting for invalid character in source code

2020-05-11 Thread Serhiy Storchaka



Change by Serhiy Storchaka :


--
keywords: +patch
pull_requests: +19342
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/20033

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40594] urljoin since 3.5 incorrectly filters out double slashes

2020-05-11 Thread David Bell



New submission from David Bell :

In Python 3.5 the urljoin function was rewritten to be RFC 3986 compliant and 
fix long standing issues. In the initial rewrite duplicate slashes were added 
by accident, and so code was added to prevent that. The discussion is here: 
https://bugs.python.org/issue22118

The code within urljoin is this:

# filter out elements that would cause redundant slashes on re-joining
# the resolved_path
segments[1:-1] = filter(None, segments[1:-1])

This seems sensible, you would not want double slashes in a URL, right? The 
problem is: double slashes are perfectly legal in a URI/URL, and for reasons I 
don't understand, they are in use in the wild. The code above was written to 
remove them because urljoin accidentally introduced them, the problem is that 
it also removes intentional double slashes:

>>> urljoin("http://www.example.com/";, "this//double/path")
'http://www.example.com/this/double/path'

Where as the expected result should be:

'http://www.example.com/this//double/path'

I suggest that the fix for this is to remove the aforementioned filter code, 
e.g. remove this:

# filter out elements that would cause redundant slashes on re-joining
# the resolved_path
segments[1:-1] = filter(None, segments[1:-1])

...and remove this code too:

if base_parts[-1] != '':
# the last item is not a directory, so will not be taken into account
# in resolving the relative path
del base_parts[-1]

and instead simply add:

del base_parts[-1]

...because the last part of the split base URL should always be deleted. If the 
last element of the list (the base URL split) is an empty string, then the URL 
ended with a slash, and so we should remove the last element otherwise a double 
slash will occur when we combine it with the second parameter to urljoin. If 
the last element is not an empty string then the last part of the URL was not a 
directory, and should be removed. Thus the last element should always be 
removed. 

By following this logic the "remove all double slashes" filter is not 
necessary, because the cause of the accidental addition of double slashes is 
removed.

--
components: Library (Lib)
messages: 368623
nosy: David Bell
priority: normal
severity: normal
status: open
title: urljoin since 3.5 incorrectly filters out double slashes
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40546] Inconsistencies between PEG parser and traceback SyntaxErrors

2020-05-11 Thread Lysandros Nikolaou



Lysandros Nikolaou  added the comment:

Guido:
> I wonder if this is the fix we're looking for?

I think this is the most sensible thing to do, yes. I guess, we also have to 
change both parsers to match this behaviour, right?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40546] Inconsistencies between PEG parser and traceback SyntaxErrors

2020-05-11 Thread Guido van Rossum



Guido van Rossum  added the comment:

I would carefully think about the meaning of that line and see if there are 
other permutations, e.g. min(Len(blah), offset - 1) ?

It would,be nice to specify what we need here from both parsers and from both 
code chunks for error printing.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40477] Launcher on Catalina

2020-05-11 Thread Glenn Travis



Glenn Travis  added the comment:

I tried to report this concern under Documentation, but got shot down as 
duplicate.

I have the same results. I tried to make Launcher the default "Open With" 
application for a script, also tried dragging (and Option dragging) the script 
to the Launcher, neither worked. 

I have received several results:
1. Nothing happens
2. Preference window opens
3. Launcher window with a run button opens; the run button does nothing.

--
nosy: +TotallyLost

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

1 2 >

1 - 100 of 119 matches

Mail list logo