wyz23x2 added the comment:
A small typo in the 1st comment:
The tempfile.mktemp() function was deprecated since version 2.3; it's long ago
(nearly 17 years!). It should be removed since it causes security holes, as
stated in the tempfile doc
(https://docs.python.org/3/library/tempfile.html
Change by wyz23x2 :
--
components: +Library (Lib)
___
Python tracker
<https://bugs.python.org/issue39768>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
Reopen.
1.See https://mail.python.org/pipermail/python-dev/2019-March/156765.html and
https://owasp.org/www-community/vulnerabilities/Insecure_Temporary_File. It's
*serious*.
2.Why not use this to generate a
temporary name that an other program will create/act
Change by wyz23x2 :
--
nosy: -ZackerySpytz
___
Python tracker
<https://bugs.python.org/issue39768>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from wyz23x2 :
The auto-reply from help@python contains this:
The Python FAQ is available at
http://docs.python.org/2/faq/index.html
Why is it .org/2/faq, not .org/3/faq?
--
components: email
files: email.png
messages: 362784
nosy: barry, r.david.murray
Change by wyz23x2 :
--
nosy: -barry, r.david.murray
___
Python tracker
<https://bugs.python.org/issue39772>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
Well, I just think it's *serious*.
I respect your thoughts. If you want to close this, you can.
--
___
Python tracker
<https://bugs.python.org/issue39
wyz23x2 added the comment:
(c)
from tempfile import mktemp
# do something...
path = mktemp()
# do something... (the "path" var is not used at all)
## No Warning
--
___
Python tracker
<https://bugs.python.o
wyz23x2 added the comment:
You could add a check that does this:
(a)
from tempfile import mktemp
with open(mktemp()) as f:
# do something...
## No Warnings
(b)
from tempfile import mktemp
path = mktemp()
# do something...
with open(mktemp()) as f:
# do something...
## RuntimeWarning
wyz23x2 added the comment:
case c is used for the case that is stated in
https://mail.python.org/pipermail/python-dev/2019-March/156725.html (a
temporary name that an other program will create / act on).
--
___
Python tracker
<ht
wyz23x2 added the comment:
But I think the function should redirect to NamedTemporaryFile(delete=False).
--
___
Python tracker
<https://bugs.python.org/issue39
wyz23x2 added the comment:
Sorry, didn't realize that.
--
___
Python tracker
<https://bugs.python.org/issue39768>
___
___
Python-bugs-list mailing list
Unsub
wyz23x2 added the comment:
Sorry, in (a)(b) is should be with "open(mktemp(),'x') as f:".
--
___
Python tracker
<https://bugs.python.org/issue39768>
___
__
wyz23x2 added the comment:
I know it's hard to achieve :)
--
___
Python tracker
<https://bugs.python.org/issue39768>
___
___
Python-bugs-list mailing list
Unsub
New submission from wyz23x2 :
the tempfile.mktemp() function was deprecated since version 2.3; it's long ago
(nearly 17 years)! It should be removed since it causes security holes, as
stated in the tempfile doc
(https://docs.python.org/3/library/tempfile.html#tempfile.mktemp
Change by wyz23x2 :
--
title: Bug in 0 -> Bug in lots of 0s
___
Python tracker
<https://bugs.python.org/issue39608>
___
___
Python-bugs-lis
New submission from wyz23x2 :
Why is this?
>>> 000 # No error
0
>>> 002
SyntaxError: leading zeros in decimal integer literals are not permitted; use
an 0o prefix for octal integers
--
components: Build
mes
wyz23x2 added the comment:
2 is not supported;
So 000 should not too.
--
___
Python tracker
<https://bugs.python.org/issue39608>
___
___
wyz23x2 added the comment:
A typo in the previous comment:
>>> list(enumerate(lis,reverse=True))
[('a',0),('b',1),('c',2),('d',3)]
--
___
Python tracker
<https://bugs.python.or
New submission from wyz23x2 :
Starting from Python 2.3, the handy enumerate() was introduced.
However, I suggest to add a "reverse" parameter:
>>> lis = ['a', 'b', 'c', 'd']
>>> list(enumerate(lis))
[(0,'a'),(1,'b'),(2,'c'),(3,'d')]
>>> list(enumerate(lis,
Change by wyz23x2 :
--
components: -Demos and Tools
versions: +Python 3.9 -Python 3.8
___
Python tracker
<https://bugs.python.org/issue39192>
___
___
Python-bug
wyz23x2 added the comment:
I've written a handy tool--RelationList. This type can easily create relations
between elements in lists.
--
Added file: https://bugs.python.org/file48821/relationlist.py
___
Python tracker
<https://bugs.python.
New submission from wyz23x2 :
I've written a handy tool--RelationList. This type can easily create relations
between elements in lists.
--
components: Demos and Tools
files: relationlist.py
messages: 359197
nosy: asvetlov, dkaveshnikov, wyz23x2, yselivanov
priority: normal
severity
Change by wyz23x2 :
--
versions: +Python 3.5, Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue39893>
___
___
Python-bugs-list mailin
wyz23x2 added the comment:
My opinion:
I think No.2 makes more sense to users that visit the docs directly by
https://docs.python.org/3.8/library/lib2to3.html; they will copy the
"docs.python.org/version/library/modulename.html" format from other modules.
But I also agree it's fra
wyz23x2 added the comment:
Patch?
--
___
Python tracker
<https://bugs.python.org/issue40051>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
OK.
--
___
Python tracker
<https://bugs.python.org/issue40051>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Change by wyz23x2 :
--
components: +Library (Lib)
versions: +Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue40386>
___
___
New submission from wyz23x2 :
This behavior:
Python 3.8.2 (tags/v3.8.2:7b3ab59, Feb 25 2020, 23:03:10) [MSC v.1916 64 bit
(AMD64)] on win32
Type "help", "copyright", "credits" or "license()" for more information.
>>> import this.main
The Zen o
wyz23x2 added the comment:
Sorry, it's "of 'this' is run", not "un".
--
___
Python tracker
<https://bugs.python.org/issue40386>
___
___
Pyt
Change by wyz23x2 :
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue40386>
___
___
Python-bugs-list mailing list
Unsubscrib
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 &
New submission from wyz23x2 :
When typing this in shell:
>>> import lib2to3
>>> help(lib2to3)
The output contains this link:
--snip--
MODULE REFERENCE
https://docs.python.org/3.8/library/lib2to3 <--
The following documentation is automatically generated f
wyz23x2 added the comment:
typo: "with something else", not "wit something else". Sorry for that.
--
___
Python tracker
<https://bug
Change by wyz23x2 :
--
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue39768>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from wyz23x2 :
Sometimes, we want to remove the ending \n and sometimes replace it wit
something else, like print(). But logging doesn't support that.
I'd want a set_terminate() (Or set_end()) function that does that. I think it's
easy. Just insert this at line 1119 of __init__
New submission from wyz23x2 :
The yellow frame blinks as shown in mp4. It's annoying and isn't good to the
eyes.
--
assignee: terry.reedy
components: IDLE
messages: 368133
nosy: terry.reedy, wyz23x2
priority: normal
severity: normal
status: open
title: Yellow hint frame blinks when
wyz23x2 added the comment:
OMG, request too large. I can't upload mp4 /(ㄒoㄒ)/~~
--
___
Python tracker
<https://bugs.python.org/issue40511>
___
___
Python-bug
Change by wyz23x2 :
--
title: IDLE yellow hint frame blinks when entering () in strings -> IDLE yellow
hint frame blinks when entering () in strings in functions/classes
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
title: Yellow hint frame blinks when entering () in strings -> IDLE yellow hint
frame blinks when entering () in strings
___
Python tracker
<https://bugs.python.org/issu
New submission from wyz23x2 :
The tkinter.tix module was deprecated since Python 3.6, but nether
DeprecationWarning nor PendingDeprecationWarning is warned. It should show a
message and removal might be scheduled for 3.11/3.12.
--
components: Tkinter
messages: 376455
nosy: wyz23x2
wyz23x2 added the comment:
Ping? We will miss 3.8.6/3.9.0rc2 if it's too late!
--
___
Python tracker
<https://bugs.python.org/issue41730>
___
___
Python-bug
wyz23x2 added the comment:
OK. What should the message be? "tkinter.tix is deprecated (and will be removed
in Python 3.x), use tkinter.ttk instead"?
--
___
Python tracker
<https://bugs.python.o
Change by wyz23x2 :
--
keywords: +patch
nosy: +wyz23x2
nosy_count: 6.0 -> 7.0
pull_requests: +21245
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22186
___
Python tracker
<https://bugs.python.org/i
Change by wyz23x2 :
--
pull_requests: -21245
___
Python tracker
<https://bugs.python.org/issue41370>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
All tests have passed. Now it's time to merge!
--
___
Python tracker
<https://bugs.python.org/issue41730>
___
___
Python-bugs-list m
Change by wyz23x2 :
--
pull_requests: +21248
pull_request: https://github.com/python/cpython/pull/22186
___
Python tracker
<https://bugs.python.org/issue41
wyz23x2 added the comment:
@epaine The doc (https://docs.python.org/3/library/tkinter.tix.html) states
"This Tk extension is unmaintained and should not be used in new code.".
--
___
Python tracker
<https://bugs.python.o
Change by wyz23x2 :
--
pull_requests: +21247
pull_request: https://github.com/python/cpython/pull/22186
___
Python tracker
<https://bugs.python.org/issue41
Change by wyz23x2 :
--
pull_requests: -21248
___
Python tracker
<https://bugs.python.org/issue41370>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wyz23x2 :
--
keywords: +patch
pull_requests: +21246
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22186
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
pull_requests: -21247
___
Python tracker
<https://bugs.python.org/issue41370>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
Ping...
--
___
Python tracker
<https://bugs.python.org/issue41730>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
Can any core reviewer review the PR?
--
___
Python tracker
<https://bugs.python.org/issue41730>
___
___
Python-bugs-list mailin
New submission from wyz23x2 :
>>> (50,) * 2
(50, 50)
>>> 50, * 2
Traceback (most recent call last):
File "", line 2, in
TypeError: 'int' object is not iterable
This message is confusing. It isn't clear that 50.__iter__ is called.
tuple(50)*2 seems to happen, wh
wyz23x2 added the comment:
>>> '1', * 2
Traceback (most recent call last):
File "", line 3, in
TypeError: 'int' object is not iterable
Update: 2.__iter__ seems to be called.
--
___
Python tracker
<https://bugs
wyz23x2 added the comment:
Just updated to 3.9. Fixed.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from wyz23x2 :
Release candidate is "rc" not "c";
Python 2.x is not supported anymore.
--
assignee: docs@python
components: Documentation
messages: 375583
nosy: docs@python, wyz23x2
priority: normal
severity: normal
status: open
title: Correct wrong
wyz23x2 added the comment:
GH-21915 submitted.
--
___
Python tracker
<https://bugs.python.org/issue41573>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wyz23x2 :
--
keywords: +patch
pull_requests: +21031
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21915
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/issue40051>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
Ping? Which of the 3 should we choose?
--
versions: +Python 3.10
___
Python tracker
<https://bugs.python.org/issue40051>
___
___
Pytho
wyz23x2 added the comment:
+1. I observe it too.
--
nosy: +wyz23x2
___
Python tracker
<https://bugs.python.org/issue41526>
___
___
Python-bugs-list mailin
wyz23x2 added the comment:
Since '/' was introduced in Python 3.8, support for positional parameters
should be supported too.
--
nosy: +wyz23x2
versions: +Python 3.9
___
Python tracker
<https://bugs.python.org/issue33
Change by wyz23x2 :
--
versions: +Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue41169>
___
___
Python-bugs-list mailin
Change by wyz23x2 :
--
title: Idle: __future__ does not work in startup code. -> IDLE: __future__ does
not work in startup code.
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
versions: +Python 3.7, Python 3.9
___
Python tracker
<https://bugs.python.org/issue40938>
___
___
Python-bugs-list mailing list
Unsub
New submission from wyz23x2 :
There is a function hex(number, /), and float objects have a method hex().
When something like 1.3.hex( is typed, the yellow box's first line contains
hex(number, /). But the method is actually hex(), no arguments. It confuses
users.
And when 1.3.list( is typed
Change by wyz23x2 :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue41075>
___
___
Python-bugs-list
Change by wyz23x2 :
--
versions: +Python 3.10
___
Python tracker
<https://bugs.python.org/issue40360>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from wyz23x2 :
The current syntax is this for thousand separators:
f'{var:,}'
It will return this when var is 1234567:
'1,234,567'
But sometimes we need a way to insert them in other places. For example:
123456789 → '1,2345,6789' (4)
62938757312 → '6,29387,57312' (5)
This could
wyz23x2 added the comment:
Q: Why not use f"{var:,}".replace(',', sepchar) for the sepchar parameter?
A: It is very complicated in the case below:
num = 1234567
text = 'Hello, world!'
print(f"{num:,}{text}").replace(',', ' ') # Becomes '1 234 567Hello world!'
print(f
New submission from wyz23x2 :
__future__.barry_as_FLUFL turns x!=y into x<>y.
But the doc by help() says:
Help on _Feature in module __future__
wyz23x2 added the comment:
Help on _Feature in module __future__ object:
class
Change by wyz23x2 :
--
components: +Library (Lib)
versions: +Python 3.10, Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue41
Change by wyz23x2 :
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue41251>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from wyz23x2 :
Python supports "/" and "\" separators on Windows.
So in IDLE, the path shown sometimes is:
D:\xxx\xxx
Sometimes is:
D:/xxx/xxx
That isn't right.
--
assignee: terry.reedy
components: IDLE
messages: 372395
nosy: terry.reedy, wyz2
wyz23x2 added the comment:
Doesn't work? The and work perfectly in 3.8.3!
Th problem now is that only very few people know it. There should be a clearer
way.
--
title: Add support of navigating through prev. commands in IDLE -> Make support
of navigating through prev. comma
New submission from wyz23x2 :
Terminals like CMD have support of navigating through commands with ↑↓. While
directly implementing the arrows is not good in IDLE (the use for jumping to
the prev. line in GUI is needed), there should be a good way.
Some ways:
1. Alt+↑↓. The current behavior
Change by wyz23x2 :
--
nosy: +xtreak
___
Python tracker
<https://bugs.python.org/issue41394>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
wyz23x2 added the comment:
But there's nothing in https://docs.python.org/3/tutorial/interpreter.html. It
should be stated there.
--
components: -Interpreter Core
nosy: -xtreak
title: Make '_' behavior in shell more clear -> Document '_' in interpreter in
shell tutor
wyz23x2 added the comment:
Ping?
--
___
Python tracker
<https://bugs.python.org/issue41314>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
wyz23x2 added the comment:
I think this should be documented more clearly. Or else users might feel
surprised:
>>> print(123)
123
>>> _
Traceback (most recent call last):
wyz23x2 added the comment:
There is nothing *wrong* with the syntax; it's just a regular assignment.
It's not something like `False = 4` or `while = 6` which '=' is invalid.
--
nosy: +wyz23x2
title: Syntax error rather than run time error -> SyntaxError rather than
NameError er
Change by wyz23x2 :
--
title: SyntaxError rather than NameError error -> SyntaxError rather than
NameError
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
type: -> behavior
versions: +Python 3.10, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue41384>
___
___
Py
New submission from wyz23x2 :
https://docs.python.org/3/faq/programming.html#is-it-possible-to-write-obfuscated-one-liners-in-python
https://github.com/python/cpython/blob/3.8/Doc/faq/programming.rst
The 3rd raises a NameError because reduce was moved into functools.
__import__('functools
New submission from wyz23x2 :
>>> (None and True)
>>> print(_)
False
>>> print((None and True)) # Not same?!
None
>>>
This isn't right.
P.S. What component should this be? IDLE? It's the shell, not just IDLE. Core?
Not that deep!
--
messages: 3
Change by wyz23x2 :
--
pull_requests: -20654
___
Python tracker
<https://bugs.python.org/issue41241>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by wyz23x2 :
--
pull_requests: +20655
pull_request: https://github.com/python/cpython/pull/21518
___
Python tracker
<https://bugs.python.org/issue41
Change by wyz23x2 :
--
nosy: +wyz23x2
nosy_count: 3.0 -> 4.0
pull_requests: +20654
pull_request: https://github.com/python/cpython/pull/21518
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
nosy: -wyz23x2
___
Python tracker
<https://bugs.python.org/issue41319>
___
___
Python-bugs-list mailing list
Unsubscribe:
wyz23x2 added the comment:
Is bpo-41300 related? It talks about non-ASCII in IDLE.
--
nosy: +wyz23x2
___
Python tracker
<https://bugs.python.org/issue41
New submission from wyz23x2 :
In https://docs.python.org/3/library/__future__.html:
annotations | 3.7.0b1 | *4.0* | PEP 563: Postponed evaluation of annotations
In PEP 563:
Starting with Python 3.7, a __future__ import is required to use the described
functionality. No warnings are raised
wyz23x2 added the comment:
Needs to add 10 zeros (sys.maxsize//100) to get it work. //200
doesn't work.
Python version: 3.8.4
Platform: Windows 10 2004
--
___
Python tracker
<https://bugs.python.org/issue41
New submission from wyz23x2 :
Consider this code:
import sys
sys.setrecursionlimit(sys.maxsize)
Causes this:
OverflowError: Python int too large to convert to C int
So what is the limit? It should be sys.maxsize.
These 2 also don't work:
sys.setrecursionlimit(sys.maxsize-1
Change by wyz23x2 :
--
type: -> crash
___
Python tracker
<https://bugs.python.org/issue40477>
___
___
Python-bugs-list mailing list
Unsubscrib
wyz23x2 added the comment:
Tested. 2**31-31 is the max, which is 2147483617, compared to sys.maxsize's
9223372036854775807!
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
versions: +Python 3.10, Python 3.7
___
Python tracker
<https://bugs.python.org/issu
Change by wyz23x2 :
--
components: +Library (Lib)
___
Python tracker
<https://bugs.python.org/issue41314>
___
___
Python-bugs-list mailing list
Unsubscribe:
1 - 100 of 160 matches
Mail list logo