[issue31538] mailbox does not treat external factories the same

[bpoaugust]

New submission from bpoaugust:

The default mailbox factory is mailbox.mboxMessage so I expect the following 
two statements to work the same:

messages = mailbox.mbox("test.mbox")
messages = mailbox.mbox("test.mbox", mailbox.mboxMessage)

However they do not.

The attached file generates the output:


Test
sender@invalid Thu Nov 17 00:49:30 2016
None

Test
MAILER-DAEMON Thu Sep 21 01:31:15 2017
None

Note that the original from has been lost in the second parse.

--
components: email
files: mb.py
messages: 302667
nosy: barry, bpoaugust, r.david.murray
priority: normal
severity: normal
status: open
title: mailbox does not treat external factories the same
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7
Added file: https://bugs.python.org/file47159/mb.py

___
Python tracker 

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

[issue31351] ensurepip discards pip's return code which leads to broken venvs

[Nick Coghlan]

Nick Coghlan added the comment:

3.4 and 3.5 are in security fix only mode now, so the change won't be 
backported there. However, it will be applicable to 2.7, so I've updated the 
impacted version list accordingly.

Igor's suggested approach in the PR looks reasonable to me as a first step, as 
it focuses just on the command line interface, and defers the question of how 
to handle error reporting in the ensurepip.bootstrap() API.

For ensurepip.bootstrap(), I'm then inclined to leave it alone in the 
maintenance releases, and have it start raising an exception for pip failures 
in 3.7+

--
stage: patch review -> commit review
versions: +Python 2.7 -Python 3.4, Python 3.5

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[Antoine Pitrou]

Antoine Pitrou added the comment:

> If it works well, maybe it's worth it to backport the change to the 3.6 
> branch. We still backport a lot of changes to 3.6. But maybe wait until 3.6.3 
> final is released?

Fair enough. Does someone want to do the backport? :-)

--

___
Python tracker 

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

[issue30788] email.policy.SMTP.fold() issue for long filenames with spaces

[Joel Hillacre]

Joel Hillacre added the comment:

I just took a quick peek at your PR to see if a similar test exists from this 
bug and it is looking good. Thanks for your work.

--

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[STINNER Victor]

STINNER Victor added the comment:

If it works well, maybe it's worth it to backport the change to the 3.6 branch. 
We still backport a lot of changes to 3.6. But maybe wait until 3.6.3 final is 
released?

--

___
Python tracker 

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

[issue29298] argparse fails with required subparsers, un-named dest, and empty argv

[Éric Araujo]

Changes by Éric Araujo :


--
assignee:  -> merwok
nosy: +merwok
versions: +Python 2.7, Python 3.7

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[STINNER Victor]

STINNER Victor added the comment:


New changeset b091bec824137f286b22084be5f8d397d21b9abb by Victor Stinner 
(Antoine Pitrou) in branch 'master':
bpo-31536: Avoid wholesale rebuild after `make regen-all` (#3678)
https://github.com/python/cpython/commit/b091bec824137f286b22084be5f8d397d21b9abb


--
nosy: +haypo

___
Python tracker 

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

[issue29298] argparse fails with required subparsers, un-named dest, and empty argv

[Anthony Sottile]

Changes by Anthony Sottile :


--
keywords: +patch
pull_requests: +3669
stage:  -> patch review

___
Python tracker 

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

[issue9253] argparse: optional subparsers

[Éric Araujo]

Éric Araujo added the comment:

The other PR is now merged in 3.7, and won’t be backported (it changes default 
behaviour and adds a new param).

--

___
Python tracker 

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

[issue9253] argparse: optional subparsers

[Éric Araujo]

Changes by Éric Araujo :


--
dependencies: +[argparse] Add required argument to add_subparsers
versions: +Python 3.7 -Python 3.3

___
Python tracker 

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

[issue26510] [argparse] Add required argument to add_subparsers

[Éric Araujo]

Changes by Éric Araujo :


--
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

___
Python tracker 

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

[issue26510] [argparse] Add required argument to add_subparsers

[Éric Araujo]

Éric Araujo added the comment:


New changeset aaf6fc0982c916cb71d9e0afcd7dda4ba495793b by Éric Araujo (Anthony 
Sottile) in branch 'master':
bpo-26510: make argparse subparsers required by default (#3027)
https://github.com/python/cpython/commit/aaf6fc0982c916cb71d9e0afcd7dda4ba495793b


--

___
Python tracker 

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

[issue31415] Add -X option to show import time

[Brett Cannon]

Brett Cannon added the comment:

Ah, OK. Then I wouldn't put it in square brackets as it seems to suggest it's 
somehow disconnected from the number.

--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Mariatta Wijaya]

Mariatta Wijaya added the comment:

Fixed and backported.
Thanks everyone!

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Mariatta Wijaya]

Mariatta Wijaya added the comment:


New changeset 5b6452d412b5be45f265093e75563fcf6d05dc3e by Mariatta (Christian 
Heimes) in branch '2.7':
bpo-31533: fix broken link to OpenSSL docs (GH-3674) (GH-3676)
https://github.com/python/cpython/commit/5b6452d412b5be45f265093e75563fcf6d05dc3e


--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Mariatta Wijaya]

Mariatta Wijaya added the comment:


New changeset 6b44ad1abdb9b3aaf27e2ba1fc4b69b9a0f50c25 by Mariatta (Miss 
Islington (bot)) in branch '3.6':
bpo-31533: fix broken link to OpenSSL docs (GH-3674) (GH-3675)
https://github.com/python/cpython/commit/6b44ad1abdb9b3aaf27e2ba1fc4b69b9a0f50c25


--

___
Python tracker 

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

[issue31537] Bug in readline module documentation example

[bazwal]

New submission from bazwal:

The second example in the readline module docs uses 
readline.get_history_length() (lines 8 & 14) where it should use 
readline.get_current_history_length().

--
assignee: docs@python
components: Documentation
messages: 302655
nosy: bazwal, docs@python
priority: normal
severity: normal
status: open
title: Bug in readline module documentation example
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue31532] Py_GetPath, Py_SetPath memory corruption due to mixed PyMem_New micex with PyMem_Raw_Free

[Vincent Gatine]

Changes by Vincent Gatine :


--
nosy: +nurelin

___
Python tracker 

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

[issue31532] Py_GetPath, Py_SetPath memory corruption due to mixed PyMem_New micex with PyMem_Raw_Free

[Vincent Gatine]

Changes by Vincent Gatine :


--
keywords: +patch
pull_requests: +3668
stage:  -> patch review

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[Antoine Pitrou]

Antoine Pitrou added the comment:

Note that GNU install (`install -C`) would probably do the trick, but is not 
necessarily installed on the build system.

--

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[Antoine Pitrou]

Antoine Pitrou added the comment:

Posted https://github.com/python/cpython/pull/3678 which uses a separate 
utility.  It seems to save 1 minute off the build step on Travis-CI.

--

___
Python tracker 

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

[issue31536] `make regen-all` triggers wholesale rebuild

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
title: `make regen-opcode` triggers wholesale rebuild -> `make regen-all` 
triggers wholesale rebuild

___
Python tracker 

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

[issue31536] `make regen-opcode` triggers wholesale rebuild

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
pull_requests: +3667

___
Python tracker 

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

[issue31536] `make regen-opcode` triggers wholesale rebuild

[Antoine Pitrou]

Antoine Pitrou added the comment:

Looks like `pgen` will also have to be changed, which is more annoying as it's 
written in C...

Perhaps another approach can be used that will use a separate utility to do the 
copying if the contents changed?

--

___
Python tracker 

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

[issue31536] `make regen-opcode` triggers wholesale rebuild

[Antoine Pitrou]

Antoine Pitrou added the comment:

Note that at least `make regen-ast` will also need to be changed in order to 
reduce build times on Travis-CI.

--

___
Python tracker 

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

[issue31536] `make regen-opcode` triggers wholesale rebuild

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
keywords: +patch
pull_requests: +3666
stage:  -> patch review

___
Python tracker 

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

[issue31443] Possibly out of date C extension documentation

[R. David Murray]

R. David Murray added the comment:

We do not currently officially support cygwin.  There are people working on 
getting it working again (and having a buildbot) so we can support it, so 
cygwin support is a goal, but not currently a requirement.  I've nosied Erik 
Brey, who is one of the main people interested in and working on cygwin.  The 
note might well be out of date even with regards to cygwin.

--
nosy: +erik.bray, r.david.murray

___
Python tracker 

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

[issue31536] `make regen-opcode` triggers wholesale rebuild

[Antoine Pitrou]

New submission from Antoine Pitrou:

`make regen-opcode` always writes the destination unconditionally, after which 
`make` thinks it has to rebuild everything.

--
components: Build
messages: 302649
nosy: pitrou, serhiy.storchaka, twouters
priority: normal
severity: normal
status: open
title: `make regen-opcode` triggers wholesale rebuild
type: enhancement
versions: Python 3.7

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Christian Heimes]

Changes by Christian Heimes :


--
pull_requests: +3665

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Christian Heimes]

Christian Heimes added the comment:


New changeset 19e4d9346db7fb65845b98a9cb9caacaaac8a81a by Christian Heimes 
(Felipe) in branch 'master':
bpo-31533: fix broken link to OpenSSL docs (#3674)
https://github.com/python/cpython/commit/19e4d9346db7fb65845b98a9cb9caacaaac8a81a


--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Roundup Robot]

Changes by Roundup Robot :


--
pull_requests: +3664

___
Python tracker 

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

[issue31482] random.seed() doesn't work with bytes and version=1

[Mariatta Wijaya]

Mariatta Wijaya added the comment:

Backport was done. Thanks.

--
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

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

[issue31443] Possibly out of date C extension documentation

[Stefan Krah]

Stefan Krah added the comment:

I've just asked on python-dev if Cygwin is still broken. Not sure
if we support it.

--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Roundup Robot]

Changes by Roundup Robot :


--
keywords: +patch
pull_requests: +3663
stage: needs patch -> patch review

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Felipe]

Felipe added the comment:

Sure, will do!

--

___
Python tracker 

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

[issue1230540] sys.excepthook doesn't work in threads

[Antoine Pitrou]

Antoine Pitrou added the comment:

Matt, do you want to post your patch here?

--

___
Python tracker 

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

[issue31443] Possibly out of date C extension documentation

[Christian Heimes]

Christian Heimes added the comment:

Do we still support cygwin?

--

___
Python tracker 

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

[issue31443] Possibly out of date C extension documentation

[Stefan Krah]

Stefan Krah added the comment:

Thanks, Christian. -- I found that in the docs the culprit is Cygwin:

   db6a569de7ae595ada53b618fce6bbbd1c98d350

--

___
Python tracker 

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

[issue26510] [argparse] Add required argument to add_subparsers

[Éric Araujo]

Changes by Éric Araujo :


--
assignee:  -> merwok
nosy: +merwok
stage:  -> commit review
versions: +Python 3.7 -Python 3.5

___
Python tracker 

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

[issue31516] current_thread() becomes "dummy" thread during shutdown

[Tim Peters]

Tim Peters added the comment:

Ya, it's clearly best for `current_thread()` to deliver consistent results.

--

___
Python tracker 

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

[issue31500] IDLE: Tiny font on HiDPI display

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

The limit 1.4 is not arbitrary. This is a minimal scale for which fonts from 10 
to 14 pixels are not decreased when converted to points (with multiplier 0.75 
and one rounding). round(14 * 0.75) = round(10.5) = 10; 10 * 1.4 = 14.

--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Mariatta Wijaya]

Mariatta Wijaya added the comment:

Cool! I'm tagging this as an easy issue, suitable for first timers or new 
contributors. 

Felipe, are you up for preparing the PR?

--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Felipe]

Felipe added the comment:

Woops. Apologies -- I somehow deleted that part from the report. Thanks Antoine 
for jumping in. If you are using the wiki url, make sure not to include the 
question mark at the end :-)

--

___
Python tracker 

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

[issue31516] current_thread() becomes "dummy" thread during shutdown

[Antoine Pitrou]

Antoine Pitrou added the comment:

Tim, any opinion on this one?  Do you agree it's an actual bug (if a bit 
obscure)?

--

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Antoine Pitrou]

Antoine Pitrou added the comment:

I don't think OpenSSL are promising anything about their URLs (the old one 
having gone 404 is proof of that :-)). So Felipe's suggestion is as good as 
any, IMHO.

--
nosy: +christian.heimes

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Mariatta Wijaya]

Mariatta Wijaya added the comment:

Thanks Antoine. So is this a matter of replacing the url to 
https://wiki.openssl.org/index.php/Manual:Ciphers(1)#CIPHER_LIST_FORMAT?
Or is there a better url that will not go out of date in the future...

--
stage:  -> needs patch
versions: +Python 2.7 -Python 3.4, Python 3.5

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Antoine Pitrou]

Antoine Pitrou added the comment:

Mariatta, that would be in the documentation for the `SSLContext.set_ciphers` 
method (in `Doc/library/ssl.rst`).

--
nosy: +pitrou

___
Python tracker 

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

[issue31516] current_thread() becomes "dummy" thread during shutdown

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
keywords: +patch
pull_requests: +3662
stage: needs patch -> patch review

___
Python tracker 

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

[issue31535] configparser unable to write comment with a upper cas letter

[Philippe Wagnieres]

New submission from Philippe Wagnieres:

I create entry with this:

   self.settings.set('General', 'Initial filter', 'All file (*.*)')
   self.settings.set('General', '# 1 => Text files (*.txt)')
   self.settings.set('General', '# 2 => CSV files (*.csv)')
   self.settings.set('General', '# 3 => Text files (*.txt) \n')

and after writing in a file:
   initial filter = All file (*.*)
   ; 1 => text files (*.txt)
   ; 2 => csv files (*.csv)
   # 3 => text files (*.txt) 

(; or # to test if differ)

It is normal or not?

Thank & Best Regards

--
messages: 302633
nosy: philippewagnie...@hispeed.ch
priority: normal
severity: normal
status: open
title: configparser unable to write comment with a upper cas letter
type: enhancement
versions: Python 3.6

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Mariatta Wijaya]

Mariatta Wijaya added the comment:

Where in the docs is this `OpenSSL cipher list format` link located?

--
nosy: +Mariatta

___
Python tracker 

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

[issue31530] Python 2.7 readahead feature of file objects is not thread safe

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

On 20.09.2017 17:22, Guido van Rossum wrote:
> 
>> Why not simply document the fact that read ahead in Python 2.7
>> is not thread-safe and leave it at that ?
> 
> Program bugs should not crash the interpreter. (ctypes excepted.)

Ideally not, agreed :-)

--
title: [2.7] Python 2.7 readahead feature of file objects is not thread safe -> 
Python 2.7 readahead feature of file objects is not thread safe

___
Python tracker 

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

[issue31534] python 3.6.2 installation failed 0x80070002 error

[roie]

New submission from roie:

hello,

i have windows 7 with 64 bit os.
i download the files:
Python 3.6.2 - 2017-07-17:
 Windows x86-64 web-based installer
 Windows x86-64 executable installer.
i clicked run as admin when i tried each one of them.


in the setup window,i clicked on "install now".
it started loading and then showed "setup failed":"0x80070002- the system 
cannot find the file specified".
i add the log file for more information.
when i searched on the internet, i didn't manage to draw information needed for 
solution on this matter. 
can you please help me figure it out?

--
components: Installation
files: Python 3.6.2 (64-bit)_20170920180757.log
messages: 302630
nosy: roie
priority: normal
severity: normal
status: open
title: python 3.6.2 installation failed 0x80070002 error
versions: Python 3.6
Added file: https://bugs.python.org/file47158/Python 3.6.2 
(64-bit)_20170920180757.log

___
Python tracker 

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

[issue31533] Dead link in SSLContext.set_ciphers documentation

[Felipe]

New submission from Felipe:

The link to the `OpenSSL cipher list format` 404s. I don't know if it's where 
the original meant to point, but the same information is available at 
https://wiki.openssl.org/index.php/Manual:Ciphers(1)#CIPHER_LIST_FORMAT

--
assignee: docs@python
components: Documentation
messages: 302629
nosy: docs@python, fov
priority: normal
severity: normal
status: open
title: Dead link in SSLContext.set_ciphers documentation
versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue31493] IDLE cond context: fix code update and font update timers

[Cheryl Sabella]

Cheryl Sabella added the comment:

Sorry, I didn't see this until now.

I added a line to editor.py in #31529 for this error message.  In _close() in 
editor.py, self.text was being set to None which wasn't calling the __del__ 
function of multicall.  I added a line to unbind "<>", 
which made the error go away.  I don't know if that's the proper fix or not, 
but it seemed the error was occurring because the `after` wasn't being removed 
at the right time.

--
nosy: +csabella

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Actually such flag already exists. It is unlocked_count.

There is also similar issue with seek().

--

___
Python tracker 

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

[issue31351] ensurepip discards pip's return code which leads to broken venvs

[Ned Deily]

Changes by Ned Deily :


--
nosy: +dstufft, ncoghlan

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +3661

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Guido van Rossum]

Guido van Rossum added the comment:

> Why not simply document the fact that read ahead in Python 2.7
> is not thread-safe and leave it at that ?

Program bugs should not crash the interpreter. (ctypes excepted.)

--

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

Ah, didn't see Benjamin's patch: much better solution :-)

--

___
Python tracker 

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

[issue31532] Py_GetPath, Py_SetPath memory corruption due to mixed PyMem_New micex with PyMem_Raw_Free

[Hartmut Goebel]

New submission from Hartmut Goebel:

When using

Py_GetPath();
Py_SetPath(pypath_w);

near the beginning of a program, Py_SetPath crashes with memory corruption if 
run on a systems with glibc's MALLOC_CHECK enabled.

The reason is: Py_GetPath and Py_SetPath use different memory interfaces.

* Py_GetPath() calls calculate_path(), which uses PyMem_New() to allocate the 
memory (see 
https://github.com/python/cpython/blob/v3.6.0/Modules/getpath.c#L738, assigned 
to `buf` first)

* But Py_SetPath() uses PyMem_RawFree() to free the memory (see 
https://github.com/python/cpython/blob/v3.6.0/Modules/getpath.c#L830).


This error DOES NOT occur on Windows, since for win32 there is a separate 
implementation, which uses PyMem_RawMalloc (see 
https://github.com/python/cpython/blob/v3.6.0/PC/getpathp.c#L378).

This error also DOES NOT occur in Python <= 3.5, since PYMEM_FUNCS have been 
the same as PYRAW_FUNCS (see 
https://github.com/python/cpython/blob/v3.5.0/Objects/obmalloc.c#L148). This 
was changed in v3.6.0: PYMEM_FUNCS now is PYOBJ_FUNCS, see 
https://github.com/python/cpython/blob/v3.6.0/Objects/obmalloc.c#L159.

This error only occurs when running on a system with glibc's MALLOC_CHECK 
enabled, which seems to be the default st least on CentOS, Fedora and ArchLinux.

Example code and relevant source see below.


Example stack trace


*** glibc detected *** ./dist/jcollect3: double free or corruption (out): 
0x7fde271ab030 ***
=== Backtrace: =
/lib64/libc.so.6[0x37f0675e66]
/lib64/libc.so.6[0x37f06789b3]
/tmp/_MEIhKg3kx/libpython3.6m.so.1.0(Py_SetPath+0x15)[0x7fde2d20e825]
./dist/jcollect3[0x4043e2]
./dist/jcollect3[0x402db2]
./dist/jcollect3[0x402fb0]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x37f061ed5d]
./dist/jcollect3[0x401a9e]
=== Memory map: 


How to reproduce
~

An example for this problem is the bootloader of PyInstaller (as of 2017-08-01).

* Make sure you are running on a Linux distribution having glibc's MALLOC_CHECK 
enabled.

* Set up a virtual environment (just too keep your system clean)

pip install 
https://github.com/pyinstaller/pyinstaller/archive/develop@%7B2017-08-01%7D.zip
echo 'print("Hello")' > test.py
pyinstaller test.py
dist/test/test  # run the frozen script

The relevant source of PyInstaller's bootloader is at 


--
components: Interpreter Core
messages: 302624
nosy: htgoebel
priority: normal
severity: normal
status: open
title: Py_GetPath, Py_SetPath memory corruption due to mixed PyMem_New micex 
with PyMem_Raw_Free
type: crash
versions: Python 3.6

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Marc-Andre Lemburg]

Marc-Andre Lemburg added the comment:

Why not simply document the fact that read ahead in Python 2.7
is not thread-safe and leave it at that ?

.next() and .readline() already don't work well together, so this
would just add one more case.

--
nosy: +lemburg

___
Python tracker 

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

[issue31525] require sqlite3_prepare_v2

[Benjamin Peterson]

Benjamin Peterson added the comment:


New changeset 525269430a3f9fbb7287e4bb6b365ac216004980 by Benjamin Peterson in 
branch 'master':
closes bpo-31525: require sqlite3_prepare_v2 (#3666)
https://github.com/python/cpython/commit/525269430a3f9fbb7287e4bb6b365ac216004980


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Benjamin Peterson]

Changes by Benjamin Peterson :


--
pull_requests: +3660
stage:  -> patch review

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Guido van Rossum]

Guido van Rossum added the comment:

@benjamin can you post your patch as a PR so you'll get credit for it?

--
nosy: +gvanrossum

___
Python tracker 

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

Re: [issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[M.-A. Lemburg]

Why not simply document the fact that read ahead in Python 2.7
is not thread-safe and leave it at that ?

.next() and .readline() already don't work well together, so this
would just add one more case.

-- 
Marc-Andre Lemburg
eGenix.com

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

[issue18875] Idle: Auto insertion of the closing parens, brackets, and braces

[Charles Wohlganger]

Charles Wohlganger added the comment:

The PR contains all the requested features, as well as mutual deletion 
(requested on PR page), and I have separated out the options for mutual 
deletion triggered by delete or triggered by backspace. I've found in usage 
that it was irritating to have both, but nice to only have one. Let users pick 
one, both, or none.

--

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

STINNER Victor added the comment:

@Serhiy: Would you like to propose a PR to implement your RuntimeError. Maybe 
we can test a few popular Python projects to see if the change would break them?

Which popular applications use threads (and files)? :-)

--

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

STINNER Victor added the comment:

Serhiy: "What if just deny reentrant reads? Set a flag while read into a 
buffer, check it before reading in other thread, and raise RuntimeError."

io.BufferedReader/io.BufferedWriter raises a RuntimeError exception for 
reentrant call, but only in the same thread. For example, it ease debug for 
signal handlers which trigger such reentrant call.

I'm not sure about 
0001-stop-crashes-when-iterating-over-a-file-on-multiple-.patch since it 
doesn't fix the consistency: two parallel readline() calls can return the same 
line, instead of being mutual exclusive and only return different lines.

I'm not sure about adding a new lock. "Lock" sounds like "dead locks". I 
dislike the risk of introducing dead locks very late in the Python 2.7 
development cycle.

I like the idea of a simple exception on concurrent operations. But I'm not 
sure how much code it will break :-/ Crazy idea: would it make sense to raise 
an exception by default, but add an opt-in option to ignore the exception? I 
wrote "crazy" since it became clear that the code is not thread-safe and so 
that parallel operations on the same file object is likely to corrupt data in 
various funny ways.

--

___
Python tracker 

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

[issue30486] Allow setting cell value

[STINNER Victor]

STINNER Victor added the comment:


New changeset 0ad05c32cc41d4c21bfd78b9ffead519ead475a2 by Victor Stinner in 
branch 'master':
bpo-30486: Make cell_set_contents() symbol private (#3668)
https://github.com/python/cpython/commit/0ad05c32cc41d4c21bfd78b9ffead519ead475a2


--
nosy: +haypo

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

STINNER Victor added the comment:

In Python 3, reading ahead is implemented by _io.BufferedReader. This object 
uses a lock to provide a prevent race condition: it's not only to prevent 
crashes, but also provide warranties on how the file is read.

If thread A calls read() first, it gets the next bytes. If thread B calls 
read() while thread A is filling the internal file buffer ("readahead 
buffer"?), the second read is queued. The file position is only controlled by a 
single thread at the same time.

_PyOS_URandom() uses a similar strategy than Benjamin's proposed patch for the 
cached file descriptor of /dev/urandom:

fd = _Py_open("/dev/urandom", O_RDONLY);
if (fd < 0) {
...
return -1;
}
if (urandom_cache.fd >= 0) {
/* urandom_fd was initialized by another thread while we were
   not holding the GIL, keep it. */
close(fd);
fd = urandom_cache.fd;
}
else {
...
urandom_cache.fd = fd;
}

The difference is that opening /dev/urandom multiple times in parallel is safe, 
whereas reading from the same file descriptor in parellel... using the buffered 
fread()... is not safe. readahead() can require multiple fread() calls, so 
multiple read() syscalls. Interlaced reads in parallel is likely to return 
scrambled data.

Adding a lock in Python 2.7.15 can impact performances even on single threaded 
applications.

I'm not sure what whaters more here: performance or correctness?

Note: Even the awesome Python 3 io module has same flaws! 
https://bugs.python.org/issue12215 "TextIOWrapper: issues with interlaced 
read-write"

The question is more *who* reads from the same file object in parallel? Does it 
make sense? :-) Do you expect that file.read(n) is "atomic" in term of 
parallelism?

Note 2: the io module is also available in Python 2.7, just not used by default 
by the builtin open() function ;-) io.open() must be used explicitly.

--
nosy: +pitrou

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

The patch is complex. What if just deny reentrant reads? Set a flag while read 
into a buffer, check it before reading in other thread, and raise RuntimeError.

--

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

STINNER Victor added the comment:

Python 3 is not affected by this bug.

In Python 3, the full I/O stack was rewritten from scratchn, the new io module 
has a different design. Reading ahead still exists in the io module, but it is 
now done by a dedicated object: io.BufferedReader, and this object uses a lock 
to prevent concurrent reads. A single thread controls the file position at the 
same time. (Except if a different thread uses directly the file descriptor, but 
that's a different story.)

--

___
Python tracker 

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

[issue25849] files, opened in unicode (text): write() returns symbols count, but seek() expect offset in bytes

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
status: open -> pending

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

STINNER Victor added the comment:

The bug was first reported to the private Python security mailing list. The 
PSRT decided that it's a regular bug and doesn't need to be categorized as a 
vulnerability, since the attacker has to be able to run arbitrary code in 
practice.

The PSRT considers that no Python 2.7 application currently rely on reading 
from the same file object "at the same time" from different thread, since it 
currently crashs.

So an attacker would have to run his/her own code... but if an attacker can 
already run arbitrary code, why relying on an unstable race condition and 
inject machine code (so not portable), whereas Python standard library is full 
of nice features to write your portable exploit?

For more information, see the Python security model:
https://python-security.readthedocs.io/security.html#security-model

--

___
Python tracker 

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

[issue31531] crash and SystemError in case of a bad zipimport._zip_directory_cache

[Oren Milman]

New submission from Oren Milman:

The following code causes the interpreter to crash (in case 'foo.zip' exists):

import zipimport
zipimport._zip_directory_cache['foo.zip'] = None
importer = zipimport.zipimporter('foo.zip')
importer.find_loader('bar')

This is because zipimport_zipimporter___init___impl() (in Modules/zipimport.c)
looks for the zipfile in _zip_directory_cache, and in case it is found, stores
its item in the new ZipImporter. Later, check_is_directory() assumes the stored
item is a dictionary, and passes it to PyDict_Contains(), which crashes.


Similarly, the following code causes a 'SystemError: new style getargs format
but argument is not a tuple':

import zipimport
importer = zipimport.zipimporter('foo.zip')
zipimport._zip_directory_cache['foo.zip']['foo\\__init__.py'] = None
importer.load_module('foo')

The same would happen if we replace the last line with
"importer.get_data('foo\\__init__.py')" or "importer.get_source('foo')".

This is because various parts of the code assume that the zipfile's item in
_zip_directory_cache is a dictionary, and that the module's item in this
dictionary is a tuple, which is eventually passed to get_data(), which passes
it to PyArg_ParseTuple(), which raises the SystemError.


Actually, I should have found this as part of #28261. ISTM that the fix for
this issue can easily also fix the issue described in #28261, by checking in
get_data() whether toc_entry is an 8-tuple.


Also, PyDict_GetItem() suppresses all errors, so in some places, e.g. in 
get_module_info(), a bad _zip_directory_cache would probably just be ignored.
But ISTM that we should raise an error saying 'invalid _zip_directory_cache'
in any place where _zip_directory_cache is accessed (in case it is invalid).

What do you think?

--
components: Extension Modules
messages: 302612
nosy: Oren Milman
priority: normal
severity: normal
status: open
title: crash and SystemError in case of a bad zipimport._zip_directory_cache
type: crash
versions: Python 3.7

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

STINNER Victor added the comment:

Benjamin Peterson proposed attached patch.

@Benjamin: Would you mind to convert this patch to a PR to ease review?

--
keywords: +patch
nosy: +benjamin.peterson, serhiy.storchaka
Added file: 
https://bugs.python.org/file47157/0001-stop-crashes-when-iterating-over-a-file-on-multiple-.patch

___
Python tracker 

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

[issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe

[STINNER Victor]

New submission from STINNER Victor:

Reading from the same file object in different threads does crash Python 2.7. 
The readahead feature of Objects/fileobject.c is not thread safe.

Try attached script to reproduce the crash.

--
components: Interpreter Core
files: readahead.py
messages: 302610
nosy: haypo
priority: normal
severity: normal
status: open
title: [2.7] Python 2.7 readahead feature of file objects is not thread safe
versions: Python 2.7
Added file: https://bugs.python.org/file47156/readahead.py

___
Python tracker 

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

[issue31529] IDLE: Add docstrings and tests for editor.py reload functions

[Cheryl Sabella]

Changes by Cheryl Sabella :


--
keywords: +patch
pull_requests: +3659
stage:  -> patch review

___
Python tracker 

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

[issue31529] IDLE: Add docstrings and tests for editor.py reload functions

[Cheryl Sabella]

New submission from Cheryl Sabella:

Add docstrings and unit tests for a subset of functions in editor.py, including 
functions related to creating the menubar, adding keybinding events, and 
reloading the editor from configdialog.

--
assignee: terry.reedy
components: IDLE
messages: 302609
nosy: csabella, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE: Add docstrings and tests for editor.py reload functions
type: enhancement
versions: Python 3.7

___
Python tracker 

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

[issue30486] Allow setting cell value

[STINNER Victor]

Changes by STINNER Victor :


--
pull_requests: +3658

___
Python tracker 

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

[issue31509] test_subprocess hangs randomly on AMD64 Windows10 3.x

[STINNER Victor]

STINNER Victor added the comment:

As expected, I'm unable to reproduce the bug on my Windows VM, even using 
--forever during 1 hour:
python -m test test_subprocess -v --timeout=120 --forever.

--

___
Python tracker 

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

[issue31500] IDLE: Tiny font on HiDPI display

[Cheryl Sabella]

Cheryl Sabella added the comment:

The scaling factor of 1.4 worked and the menu and configdialog looked normal.

font['size'] = 9 also worked as did font['size'] = 10.  font['size'] = 12 is 
when it's too big.

--

___
Python tracker 

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

[issue31498] Default values for zero in time.strftime()

[Denis Osipov]

Changes by Denis Osipov :


--
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

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

[issue31517] MainThread association logic is fragile

[Nick Coghlan]

Nick Coghlan added the comment:

We had the quirks of import related threading deadlocks documented for a long 
time, not as a promise, but as a debugging aid (and a recommendation for "don't 
do that").

I'd see this as being similar: we'd document that if you're using the _thread 
module, or otherwise allowing operating system threads not managed by the 
threading module to call in and run arbitrary Python code, then you should run 
"import threading" early in the actual main thread to make sure it gets 
associated correctly.

--

___
Python tracker 

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

[issue31500] IDLE: Tiny font on HiDPI display

[Terry J. Reedy]

Terry J. Reedy added the comment:

My screen is 23.5 x 13.25, making it 109 DPI.  I asked Cheryl to try 9 first 
because it is 3/4 of 12.

--

___
Python tracker 

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

[issue31528] Let ConfigParser parse systemd units

[林自均]

New submission from 林自均:

Although systemd units are inspired by .ini format, ConfigParser is unable to 
parse those files because:

1. Multiple assignments to the same option in systemd units are concatenated 
with white spaces.
2. Multiple sections with the same section name are merged.
3. An option assignment of empty value resets the option.

I suggest 3 corresponding parameters in ConfigParser.__init__():

1. merge_options: If set to True, multiple assignment to the same option are 
concatenated with white spaces. Default is False.
2. merge_sections: If set to True, multiple sections with the same name are 
merged. Default is False.
3. empty_is_reset: Only relevant when merge_options is True. If set to True, an 
option assignment of empty value will reset the option. Default is False.

--
components: Library (Lib)
messages: 302604
nosy: johnlinp
priority: normal
severity: normal
status: open
title: Let ConfigParser parse systemd units
type: enhancement
versions: Python 3.7

___
Python tracker 

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

[issue31517] MainThread association logic is fragile

[Antoine Pitrou]

Antoine Pitrou added the comment:

I'm not sure this is an issue worth fixing, but I don't think it's a good idea 
to document such quirky semantics.

--

___
Python tracker 

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

[issue31517] MainThread association logic is fragile

[Antoine Pitrou]

Antoine Pitrou added the comment:

> That said, I do agree with Tim that the status quo isn't broken per se: we 
> renamed `thread` to `_thread` in Python 3 for a reason

This is not caused by `_thread` specifically, but any background thread created 
by C code that might invoke Python code.  The reproducer just uses the 
`_thread` module out of convenience.

--

___
Python tracker 

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

[issue31517] MainThread association logic is fragile

[Antoine Pitrou]

Antoine Pitrou added the comment:

> Is there a problem here?  I haven't heard of anyone even wondering about this 
> before.

This came while working on the PEP 556 implementation.

--

___
Python tracker 

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

[issue31508] Running test_ttk_guionly logs "test_widgets.py:1562: UserWarning: Deprecated API of Treeview.selection() should be removed" warnings

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +3657

___
Python tracker 

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

[issue27319] Multiple item arguments for selection operations

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
pull_requests: +3656

___
Python tracker 

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

[issue31508] Running test_ttk_guionly logs "test_widgets.py:1562: UserWarning: Deprecated API of Treeview.selection() should be removed" warnings

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Oh, I missed that the selection() method with its current behavior is 
documented in the module documentation. It isn't undocumented implementation 
detail. This raises a bar for removing higher.

I think it is better to defer removing to 3.8 or later. Instead we should 
document the deprecation.

--

___
Python tracker 

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

[issue31506] Improve the error message logic for object_new & object_init

[Nick Coghlan]

Nick Coghlan added the comment:

Aye, the "C.__new__" example omitting the first arg was just an error in that 
example.

And that's a good point about the current "object.__init__()" error message 
actually being incorrect, since the *methods* each take exactly one argument - 
it's only the "object(*args, **kwds)" form that genuinely expects zero 
arguments.

If we were to correct that error as well, we'd end up with the following:

# Without any method overrides
class C:
pass

C(42) -> "TypeError: C() takes no arguments"
C.__new__(C, 42) -> "TypeError: C() takes no arguments"
C().__init__(42) -> "TypeError: C.__init__() takes exactly one argument"
# These next two quirks are the price we pay for the nicer errors above
object.__new__(C, 42) -> "TypeError: C() takes no arguments"
object.__init__(C(), 42) -> "TypeError: C.__init__() takes exactly one 
argument"

# With method overrides
class D:
def __new__(cls, *args, **kwds):
super().__new__(cls, *args, **kwds)
def __init__(self, *args, **kwds):
super().__init__(*args, **kwds)

D(42) -> "TypeError: object.__new__() takes exactly one argument"
D.__new__(D, 42) -> "TypeError: object.__new__() takes exactly one argument"
D().__init__(42) -> "TypeError: object.__init__() takes exactly one 
argument"
object.__new__(C, 42) -> "TypeError: object.__new__() takes exactly one 
argument"
object.__init__(C(), 42) -> "TypeError: object.__init__() takes exactly one 
argument"

--

___
Python tracker 

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

[issue31508] Running test_ttk_guionly logs "test_widgets.py:1562: UserWarning: Deprecated API of Treeview.selection() should be removed" warnings

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thank you Cheryl. I'll open a separate issue.

--

___
Python tracker 

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

[issue31527] Report details of excess arguments in object_new & object_init

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

str(x=1) is not the best example since str() takes keyword arguments. Look at 
tuple() and list():

>>> tuple(x=1)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: tuple() takes no keyword arguments
>>> list(x=1)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: list() takes no keyword arguments

Initial version of my patch for issue31506 reported error messages similar to 
tuple() and list(), but at end I simplified it since in any case the error 
message was not perfect.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue31506] Improve the error message logic for object_new & object_init

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

C.__new__(42) emits different error, "TypeError: object.__new__(X): X is not a 
type object (int)". Perhaps you meant C.__new__(C, 42) which now emits 
"TypeError: C() takes no arguments".

Messages "object.__new__() takes no arguments" and "object.__init__() takes no 
arguments" are not correct since both object.__new__() and object.__init__() 
take one argument -- a class and an instance correspondingly.

--

___
Python tracker 

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