[issue27313] test case failures in test_widgets.ComboboxTest.of test_ttk_guionly on OS X with Cocoa Tk 8.5.18

[Ned Deily]

Ned Deily  added the comment:


New changeset 1dee4565fae9ccb54719fa99d7944c148736083a by Ned Deily (Miss 
Islington (bot)) in branch '3.6':
bpo-27313: Avoid test_ttk_guionly ComboboxTest fail with macOS Cocoa Tk 
(GH-12011) (GH-12013)
https://github.com/python/cpython/commit/1dee4565fae9ccb54719fa99d7944c148736083a


--

___
Python tracker 

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

[issue26386] tkinter - Treeview - .selection_add and selection_toggle

[Ned Deily]

Change by Ned Deily :


--
pull_requests: +12045

___
Python tracker 

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

[issue27313] test case failures in test_widgets.ComboboxTest.of test_ttk_guionly on OS X with Cocoa Tk 8.5.18

[miss-islington]

miss-islington  added the comment:


New changeset 25d20a6503f3cd4ff8cf0e8ee33eea2b1daa77a8 by Miss Islington (bot) 
in branch '3.7':
bpo-27313: Avoid test_ttk_guionly ComboboxTest fail with macOS Cocoa Tk 
(GH-12011)
https://github.com/python/cpython/commit/25d20a6503f3cd4ff8cf0e8ee33eea2b1daa77a8


--
nosy: +miss-islington

___
Python tracker 

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

[issue27313] test case failures in test_widgets.ComboboxTest.of test_ttk_guionly on OS X with Cocoa Tk 8.5.18

[miss-islington]

Change by miss-islington :


--
pull_requests: +12043

___
Python tracker 

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

[issue27313] test case failures in test_widgets.ComboboxTest.of test_ttk_guionly on OS X with Cocoa Tk 8.5.18

[Ned Deily]

Ned Deily  added the comment:


New changeset aeca373b339e0ea9739536ce6b43bd90f3b89873 by Ned Deily in branch 
'master':
bpo-27313: Avoid test_ttk_guionly ComboboxTest fail with macOS Cocoa Tk 
(GH-12011)
https://github.com/python/cpython/commit/aeca373b339e0ea9739536ce6b43bd90f3b89873


--

___
Python tracker 

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

[issue27313] test case failures in test_widgets.ComboboxTest.of test_ttk_guionly on OS X with Cocoa Tk 8.5.18

[miss-islington]

Change by miss-islington :


--
pull_requests: +12044

___
Python tracker 

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

[issue24090] Add a "copy value to clipboard" option to the debugger

[Terry J. Reedy]

Terry J. Reedy  added the comment:

The squeezer feature added last summer can be used to copy large output in 
Shell to the clipboard.  '>>> [None]*1' results in a squeezer label 
representing 750 wrapped lines.  Note that pasting into a new editor disables 
it for awhile.  (Editor does not wrap).  Pasting into command prompt is not 
good either.  Notepad++ handles the 6 char line pretty well.

I am not sure what I was thinking about a block copy in Shell.  If a block is 
selected, it is easily copied.

My thinking now is that large output in the debugger should be squeezed, at a 
much lower threashhold than in Shell.  It is designed for values of, say, 40 
chars or less.  'Large' values could then be copied to clipboard or displayed 
in a separate viewer.

--
versions: +Python 3.8 -Python 3.4

___
Python tracker 

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

[issue27313] test case failures in test_widgets.ComboboxTest.of test_ttk_guionly on OS X with Cocoa Tk 8.5.18

[Ned Deily]

Change by Ned Deily :


--
keywords: +patch
pull_requests: +12042
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

[issue1442493] IDLE shell window gets very slow when displaying long lines

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Squeezer was added last summer, and definitely helps, but I still intend to 
consider other points raised here.

--

___
Python tracker 

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

[issue1442493] IDLE shell window gets very slow when displaying long lines

[Terry J. Reedy]

Change by Terry J. Reedy :


--
versions: +Python 3.8 -Python 2.7, Python 3.3, Python 3.4, Python 3.7

___
Python tracker 

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

[issue36045] builtins.help function is not much help with async functions

[Roundup Robot]

Change by Roundup Robot :


--
keywords: +patch
pull_requests: +12041
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

[issue23216] IDLE grep/find/replace source code needs docstrings

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Current module names, docstring status, and note.

grep - present, some args not doc'ed
replace - spotty; do not repetively doc 'event=None' args
search - ditto
searchbase - present
searchengine - present; do not separately docstring 'isxyz' wrappers

Closing """ must be on line by itself.

Parts of the patch should be usable at least as 'first drafts' for filling in 
missing docstrings.  I am not sure whether better to edit diff (maybe after 
splitting into diffs for each module) and apply (I have never done this with 
git) or to edit modules directly.

Cheryl, another one you might want to grab.

--
nosy: +cheryl.sabella
stage: patch review -> needs patch
versions: +Python 3.7, Python 3.8 -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

[issue36018] Add a Normal Distribution class to the statistics module

[miss-islington]

miss-islington  added the comment:


New changeset 79fbcc597dfd039d3261fffcb519b5ec5a18df9d by Miss Islington (bot) 
(Raymond Hettinger) in branch 'master':
bpo-36018: Make __pos__ return a distinct instance of NormDist (GH-12009)
https://github.com/python/cpython/commit/79fbcc597dfd039d3261fffcb519b5ec5a18df9d


--
nosy: +miss-islington

___
Python tracker 

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

[issue36099] Clarify the difference between mu and xbar in the statistics documentation

[Raymond Hettinger]

Raymond Hettinger  added the comment:

> Without necessarily defining what each means, 
> perhaps it is sufficient to change this clause in the docs

+1 That is a simple way to address the concern.

--
nosy: +rhettinger

___
Python tracker 

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

[issue23205] Unit test needed for IDLE's GrepDialog.py's findfiles()

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Findfiles was more like os.walk than os.listdir.  os.walk now uses os.scandir 
instead of os.listdir.  From 3.7.2 doc:

"By default, errors from the scandir() call are ignored. If optional argument 
onerror is specified, it should be a function; it will be called with one 
argument, an OSError instance. It can report the error to continue with the 
walk, or raise the exception to abort the walk. Note that the filename is 
available as the filename attribute of the exception object."

We should delete the try: except: and pass in a function to print the name and 
error message.  This could be done after getting a working patch.

Defaults are not needed as findfiles is called with 3 positional args.  The 
calling method should do the replacement of '' with os.curdir().

The patch must be incomplete as generators do not have a sort method.  Replace 
the first 3 lines of grep_it with

folder, filepat = os.path.split(path)
if not folder:
folder = os.curdir()
filelist = sorted(findfiles(folder, filepat, self.recvar.get())

and replace 'list' with 'filelist' in the following code.

Cheryl, grab the issue if you want to do this.

--
nosy: +cheryl.sabella
stage: patch review -> needs patch
versions: +Python 3.7, Python 3.8 -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

[issue36018] Add a Normal Distribution class to the statistics module

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Steven, Davin, Michael:  Thanks for the encouragement and taking the time to 
review this code.

--

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Raymond Hettinger]

Change by Raymond Hettinger :


--
pull_requests: +12040

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Raymond Hettinger]

Raymond Hettinger  added the comment:

> Why use object.__setattr__(self, 'mu', mu) instead of 
> self.mu = mu in the __init__ method?

The idea was the instances should be immutable and hashable, but this added 
unnecessary complexity, so I took this out prior to the check in.

> Should __pos__ return a copy rather than the instance itself?

Yes.  I'll fix that straight-way.

^ The chice of using mu versus xbar was deliberate

I concur with that choice and also prefer to stick with mu and sigma:

1) It's too late to change it elsewhere in statistics and the random modules. 
2) Having attribute names the same as function names in the same module is 
confusing. 3) I had already user tested this API in some Python courses.  4) 
The variable names match the various external sources I've linked to in the 
docs.  5)  Python historically hasn't shied from greek letter names (math: pi 
tau gamma random: alpha, better, lambd, mu, sigma).

--

___
Python tracker 

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

[issue36099] Clarify the difference between mu and xbar in the statistics documentation

[Davin Potts]

Davin Potts  added the comment:

Without necessarily defining what each means, perhaps it is sufficient to 
change this clause in the docs:
it should be the mean of data

For pvariance() it could read as:
it should be the *population* mean of data

And for variance() it could read as:
it should be the *sample* mean of data

--
nosy: +davin

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Davin Potts]

Davin Potts  added the comment:

Steven: Your point about population versus sample makes sense and your point 
that altering their names would be a breaking change is especially important.  
I think that pretty well puts an end to my suggestion of alternative names and 
says the current pattern should be kept with NormalDist.

I particularly like the idea of using the TI Nspire and Casio Classpad to guide 
or help confirm what symbols might be recognizable to secondary students or 1st 
year university students.


Raymond: As an idea for examples demonstrating the code, what about an example 
where a plot of pdf is created, possibly for comparison with cdf?  This would 
require something like matplotlib but would help to visually communicate the 
concepts of pdf, perhaps with different sigma values?

--

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Terry J. Reedy]

Change by Terry J. Reedy :


--
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

[issue36095] Better NaN sorting.

[Tim Peters]

Tim Peters  added the comment:

If we could roll back the clock, I'd impose a total ordering on floats in 
Python and supply some other way to spell 754's comparison operators (which 
users would have to ask for explicitly if they wanted to hassle with the 
near-useless and too-often-surprising "unordered" outcome).

But, too late.  As is, I don't want to mess up every context that _uses_ 
comparisons under the covers to make a special case out of NaNs.  Floats are a 
partially ordered type, and live with the consequences.

Which are approximately none for me ;-)  I rarely have a use for a NaN to begin 
with, and never in a list I intend to sort.

That said, the one thing that gives me pause is this line from numpy's docs:

   https://docs.scipy.org/doc/numpy/reference/generated/numpy.sort.html
"In numpy versions >= 1.4.0 nan values are sorted to the end."

But that's not the end of it:


https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.sort_values.html
...
na_position : {‘first’, ‘last’}, default ‘last’
first puts NaNs at the beginning, last puts NaNs at the end

So people who go down this path can't get two steps before making a fork in the 
road ;-)

--

___
Python tracker 

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

[issue33043] Add a 'Contributing to Docs' link at the bottom of docs.python.org

[Ned Deily]

Change by Ned Deily :


--
nosy: +mdk

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[miss-islington]

miss-islington  added the comment:


New changeset 38aea4131f57769d2c3d136b09172760db097605 by Miss Islington (bot) 
in branch '3.7':
bpo-24310: Document IDLE settings dialog font tab sample (GH-12007)
https://github.com/python/cpython/commit/38aea4131f57769d2c3d136b09172760db097605


--
nosy: +miss-islington

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Davin Potts]

Davin Potts  added the comment:

@Giampaolo:  The docstring in the shared_memory module currently marks the API 
as experimental.  (You read my mind...)

I will start a new PR where we can work on the 
better-integration-into-the-larger-multiprocessing-docs and add comments there.

--

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Davin Potts]

Davin Potts  added the comment:


New changeset e895de3e7f3cc2f7213b87621cfe9812ea4343f0 by Davin Potts in branch 
'master':
bpo-35813: Tests and docs for shared_memory (#11816)
https://github.com/python/cpython/commit/e895de3e7f3cc2f7213b87621cfe9812ea4343f0


--

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[miss-islington]

Change by miss-islington :


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

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Terry J. Reedy]

Terry J. Reedy  added the comment:


New changeset d610116a2e48b55788b62e11f2e6956af06b3de0 by Terry Jan Reedy in 
branch 'master':
bpo-24310: Document IDLE settings dialog font tab sample (GH-12007)
https://github.com/python/cpython/commit/d610116a2e48b55788b62e11f2e6956af06b3de0


--

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Ned Deily]

Change by Ned Deily :


--
nosy:  -ned.deily

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I don't think one 4-years-old anonymous report missing essential details, and 
not verified since, is sufficient to drive a doc change, especially since the 
Mac installer has switched from recommending ActiveState 8.5.18 to installing 
our own compilation of 8.6.8.  

On my MacBook Air with Mohave and 3.7.2, I added 'p__g' to the top of IDLE 
settings dialog font tab text sample and looked for glitches with various fonts 
and sizes. The only thing I found was with Optima 13.  The 'g' was the double 
loop ('eyeglasses') form and a bit of the bottom of the lower loop was gone or 
thin.  It was still easily recognized and the 'p__' part was unaffected.

I decided to document use of the font sample, including the possibility of 
changing face and size to avoid glitches.  Since the procedure is generic for 
any platform or character, I did not specify Mac or 'p_g'.

--
assignee:  -> terry.reedy
nosy: +ned.deily, terry.reedy
stage: patch review -> 
versions:  -Python 2.7

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Ned Deily]

Change by Ned Deily :


--
nosy:  -ned.deily

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Ned Deily]

Ned Deily  added the comment:

Sorry this issue slipped off my radar.  Terry's new PR 12007 provides a more 
general documentation update such that the I no longer think the tcltk page 
should be updated.  Removing myself.

--
assignee: ned.deily -> 
versions: +Python 3.7, Python 3.8 -Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Steven D'Aprano]

Steven D'Aprano  added the comment:

Davin: the chice of using mu versus xbar was deliberate, as they represent 
different quantities: the population mean versus a sample mean. But reading 
over the docs with fresh eyes, I can now see that the distinction is not as 
clear as I intended.

I think that changing the names now would be a breaking change, but even if it 
wasn't, I don't want to change the names. The distinction between population 
parameters (mu) and sample statistics (xbar) is important and I think the 
function parameters should reflect that.

As for the new NormalDist class, we aren't limited by backwards compatibility, 
but I would still argue for the current names mu and sigma. As well as matching 
the population parameters of the distribution, they also matches the names used 
in calculators such as the TI Nspire and Casio Classpad (two very popular CAS 
calculators used by secondary school students).

See #36099. If you would like to suggest some doc changes, please feel free to 
do so.

--

___
Python tracker 

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

[issue36099] Clarify the difference between mu and xbar in the statistics documentation

[Steven D'Aprano]

New submission from Steven D'Aprano :

The documentation isn't clear as to the difference between mu and xbar, and why 
one is used in variance and the other in pvariance.

See #36018 for discussion.

For the record: mu or μ is the population parameter, i.e. the mean of the 
entire population, if you could average every individual. xbar or x̅  is the 
mean of a sample.

--
assignee: docs@python
components: Documentation
messages: 336424
nosy: docs@python, steven.daprano
priority: normal
severity: normal
status: open
title: Clarify the difference between mu and xbar in the statistics 
documentation
type: behavior
versions: Python 3.8

___
Python tracker 

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

[issue24310] Idle documentation -- what to do if you do not see an underscore.

[Terry J. Reedy]

Change by Terry J. Reedy :


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

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

IMHO given the size of the change and how quickly this evolved I would probably 
feel safer to mark the API as experimental (no pun intended, this is great 
work), at least in alpha2. I believe we now have a good explanation in the docs 
but it still needs to be integrated better into the larger, existing 
multiprocessing docs (I will try to add some comments on the PR tomorrow).

--

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Steven D'Aprano]

Steven D'Aprano  added the comment:

Karthikeyan: thanks for the hint about Github.

Raymond: thanks for the diff. Some comments:

Why use object.__setattr__(self, 'mu', mu) instead of self.mu = mu in the 
__init__ method?

Should __pos__ return a copy rather than the instance itself?

The rest looks good to me, and I look forward to using it.

--

___
Python tracker 

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

[issue33043] Add a 'Contributing to Docs' link at the bottom of docs.python.org

[Susan Su]

Change by Susan Su :


--
keywords: +patch
pull_requests: +12037
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

[issue21150] Add quick links table to argparse docs

[Susan Su]

Change by Susan Su :


--
keywords: +patch
pull_requests: +12036
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

[issue36095] Better NaN sorting.

[Raymond Hettinger]

Raymond Hettinger  added the comment:

This issue isn't sorting.  The issue is with what NaNs do.  You can propose to 
"fix" NaNs rather than special casing everything else in Python that compares 
two values.

A NaN could be given a deterministic sort order relative to other floats (much 
as None used to compare less than everything else),  That said, you'll find 
people who argue than NaNs aren't broken and are doing exactly what they're 
supposed to do.

Please take this to python-ideas.  From my point of view, the current proposal 
is a non-starter.

--

___
Python tracker 

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

[issue34211] Cygwin build broken due to use of _Type in static declaration in _abc module

[Inada Naoki]

Change by Inada Naoki :


--
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

[issue34211] Cygwin build broken due to use of _Type in static declaration in _abc module

[miss-islington]

Change by miss-islington :


--
pull_requests: +12035

___
Python tracker 

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

[issue36098] asyncio: ssl client-server with "slow" read

[MultiSosnooley]

New submission from MultiSosnooley :

Recently, some awesome contributors add support for implicit ssl mode for 
aioftp. But this produced some issues and one of them is not relevant to 
aioftp, but to asyncio. Here is link 
https://repl.it/@multisosnooley/asyncio-ssl-connection-with-slow-retreiving to 
reproduce. This code mimics one test of aioftp: filesystem slower, than socket 
write. Reduced code to reproduce use sleep for this purpose. So we have proper 
run without ssl (you can test this by removing ssl argument in server and 
client instantiation) and «buggy» in case of ssl. After some digging in I 
realised, that someone calls connection_lost of ssl protocol before we read all 
data from transport. Data sent by server, but client have (looks like 64k) 
buffer and since there is no transport read fails. Also, I can say (with help 
of wireshark) that in case of non-ssl connection, tcp FIN initiated by server 
(as it should be), but in case of ssl — FIN sent by client.

Direct code to reproduce
```
import ssl
import asyncio

import trustme


HOST = "127.0.0.1"
PORT = 8021

ca = trustme.CA()
server_cert = ca.issue_server_cert(HOST)

ssl_server = ssl.create_default_context(ssl.Purpose.CLIENT_AUTH)
server_cert.configure_cert(ssl_server)

ssl_client = ssl.create_default_context(ssl.Purpose.SERVER_AUTH)
ca.configure_trust(ssl_client)


async def handler(reader, writer):
writer.write(b"0" * 4 * 100 * 1024)
await writer.drain()
writer.close()
await asyncio.sleep(1)
print("handler done")


async def client():
# reader, writer = await asyncio.open_connection(HOST, PORT)
reader, writer = await asyncio.open_connection(HOST, PORT, ssl=ssl_client)
count = 0
while True:
data = await reader.read(8192)
count += len(data)
print(f"received {len(data)}, total {count}")
if not data:
break
await asyncio.sleep(0.001)
writer.close()


loop = asyncio.get_event_loop()
# start = asyncio.start_server(handler, HOST, PORT)
start = asyncio.start_server(handler, HOST, PORT, ssl=ssl_server)
server = loop.run_until_complete(start)
loop.run_until_complete(client())
server.close()
loop.run_until_complete(server.wait_closed())
```

Output:
```
received 8192, total 8192
received 8192, total 16384
received 8192, total 24576
received 8192, total 32768
received 8192, total 40960
received 8192, total 49152
received 8192, total 57344
received 8192, total 65536
received 8192, total 73728
received 8192, total 81920
received 8192, total 90112
received 8192, total 98304
received 8192, total 106496
received 8192, total 114688
received 8192, total 122880
received 8192, total 131072
received 8192, total 139264
received 8192, total 147456
received 8192, total 155648
received 8192, total 163840
received 8192, total 172032
received 8192, total 180224
received 8192, total 188416
received 8192, total 196608
received 8192, total 204800
received 8192, total 212992
received 8192, total 221184
received 8192, total 229376
received 8192, total 237568
received 8192, total 245760
received 8192, total 253952
received 8192, total 262144
received 8192, total 270336
received 8192, total 278528
received 8192, total 286720
received 8192, total 294912
received 8192, total 303104
received 8192, total 311296
received 8192, total 319488
received 8192, total 327680
received 8192, total 335872
Traceback (most recent call last):
  File "slow-data-test.py", line 46, in 
loop.run_until_complete(client())
  File "/home/poh/.pyenv/versions/3.6.7/lib/python3.6/asyncio/base_events.py", 
line 473, in run_until_complete
return future.result()
  File "slow-data-test.py", line 33, in client
data = await reader.read(8192)
  File "/home/poh/.pyenv/versions/3.6.7/lib/python3.6/asyncio/streams.py", line 
640, in read
self._maybe_resume_transport()
  File "/home/poh/.pyenv/versions/3.6.7/lib/python3.6/asyncio/streams.py", line 
408, in _maybe_resume_transport
self._transport.resume_reading()
  File "/home/poh/.pyenv/versions/3.6.7/lib/python3.6/asyncio/sslproto.py", 
line 351, in resume_reading
self._ssl_protocol._transport.resume_reading()
AttributeError: 'NoneType' object has no attribute 'resume_reading'
```

--
components: asyncio
messages: 336420
nosy: MultiSosnooley, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: asyncio: ssl client-server with "slow" read
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

___
Python tracker 

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

[issue36097] Use only public C-API in _xxsubinterpreters module.

[Eric Snow]

Change by Eric Snow :


--
keywords: +patch
pull_requests: +12034
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

[issue36097] Use only public C-API in _xxsubinterpreters module.

[Eric Snow]

New submission from Eric Snow :

After discussions about our use of the public C-API in stdlib extension 
modules, I realized that I'd written the _xxsubinterpreters module using 
internal C-API.  However, there's no reason not to stick to the public C-API.  
Fixing this will require adding a few new "private" functions.

--
assignee: eric.snow
components: Interpreter Core
messages: 336419
nosy: eric.snow
priority: normal
severity: normal
stage: needs patch
status: open
title: Use only public C-API in _xxsubinterpreters module.
versions: Python 3.8

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Brandt Bucher]

Brandt Bucher  added the comment:

Thanks for the feedback. I agree with you on the iffy delegation issue. 
However, this is problem that I feel deserves a fix... the behavior (silently 
producing garbage results) is just so un-pythonic. It’s been made clear in 
other issues that a warning isn’t right here, and sorting is guaranteed to use 
__lt__ (which NaN defines well for use in all other contexts). I honestly don’t 
see any other way. If that means fixing min, max, and friends too, I think it’s 
worth it.

Special cases justify special-casing, especially when doing so doesn’t break 
the rules. NaN isn’t like any other value of any other type; It’s practically 
defined by its ability to ruin valid comparison operations, even with fellow 
floats, for which ordering is otherwise well-defined.

For what it’s worth, I don’t know if anybody who’s tried to sort sets. Every 
Python programmer I know has blindly sorted floats at some point.

--

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Davin Potts]

Davin Potts  added the comment:

There is an inconsistency worth paying attention to in the choice of names of 
the input parameters.

Currently in the statistics module, pvariance() accepts a parameter named "mu" 
and pstdev() and variance() each accept a parameter named "xbar".  The docs 
describe both "mu" and "xbar" as "it should be the mean of data".  I suggest it 
is worth rationalizing the names used within the statistics module for 
consistency before reusing "mu" or "xbar" or anything else in NormalDist.

Using the names of mathematical symbols that are commonly used to represent a 
concept is potentially confusing because those symbols are not always 
*universally* used.  For example, students are often introduced to new concepts 
in introductory mathematics texts where concepts such as "mean" appear in 
formulas and equations not as "mu" but as "xbar" or simply "m" or other simple 
(and hopefully "friendly") names/symbols.  As a mathematician, if I am told a 
variable is named, "mu", I still feel the need to ask what it represents.  
Sure, I can try guessing based upon context but I will usually have more than 
one guess that I could make.

Rather than continue down a path of using various 
mathematical-symbols-written-out-in-English-spelling, one alternative would be 
to use less ambiguous, more informative variable names such as "mean".  It 
might be worth considering a change to the parameter names of "mu" and "sigma" 
in NormalDist to names like "mean" and "stddev", respectively.  Or perhaps 
"mean" and "standard_deviation".  Or perhaps "mean" and "variance" would be 
easier still (recognizing that variance can be readily computed from standard 
deviation in this particular context).  In terms of consistency with other 
packages that users are likely to also use, scipy.stats functions/objects 
commonly refer to these concepts as "mean" and "var".

I like the idea of making NormalDist readily approachable for students as well 
as those more familiar with these concepts.  The offerings in scipy.stats are 
excellent but they are not always the most approachable things for new students 
of statistics.

--

___
Python tracker 

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

[issue36085] Enable better DLL resolution

[Steve Dower]

Steve Dower  added the comment:

> Correct me if I'm wrong, don't process launches use the `env` kwarg for 
> Popen, not the raw os.environ['PATH']?

If you don't provide env, it'll use the current process's environment, and if 
you do provide it without copying at least some entries, chances are your 
process won't start (and in general, you copy the current value and add to it). 
I've never seen anyone try to reset PATH here, nor would I recommend it.

--

___
Python tracker 

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

[issue36096] IDLE: Refactor class variables to instance variables in colorizer

[Cheryl Sabella]

Change by Cheryl Sabella :


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

___
Python tracker 

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

[issue36096] IDLE: Refactor class variables to instance variables in colorizer

[Cheryl Sabella]

New submission from Cheryl Sabella :

>From Terry's comment on PR11472 for issue 35689: 
> I don't like the use of class variables to initialize volatile instance state 
> variables. I think it confuses the code a bit. Better, I think, to put them 
> in an `init_state` method called from `__init__`. (I am not sure if method 
> could be used in tests.) Since the tests do not access the class vars 
> directly on the class, they should not be affected. I am leaving this minor 
> refactoring for another issue after merging the tests. Then we can modify the 
> class docstring.

--
assignee: terry.reedy
components: IDLE
messages: 336415
nosy: cheryl.sabella, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE: Refactor class variables to instance variables in colorizer
type: enhancement
versions: Python 3.7, Python 3.8

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Okay, it's in for the second alpha.  Please continue to make API or 
implementation suggestions.  Nothing is set in stone.

--

___
Python tracker 

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

[issue36018] Add a Normal Distribution class to the statistics module

[Raymond Hettinger]

Raymond Hettinger  added the comment:


New changeset 11c79531655a4aa3f82c20ff562ac571f40040cc by Raymond Hettinger in 
branch 'master':
bpo-36018: Add the NormalDist class to the statistics module (GH-11973)
https://github.com/python/cpython/commit/11c79531655a4aa3f82c20ff562ac571f40040cc


--

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Raymond Hettinger]

Raymond Hettinger  added the comment:

-1 I am flat opposed to special casing the list.sort() code for the specific 
case of NaNs.  

This is an incorrect delegation of responsibility.  The sorted objects are 
responsible for saying how they will sort and whether than is. deterministic.  
Note, float('NaN') isn't the only case.  Sets objects only have a partial 
ordering.

Also note that list.sort() isn't the only tool that compares objects.  There is 
also min(), max(), heaps, bisect, etc.  For the most part, we've able to keep 
those all it sync with one another by a clear separation of responsibilities 
(objects decide how they are compared versus tools that use comparisons).

At the very least, this would need a python-ideas discussion. FWIW, the usual 
solution to this problem is to strip the NaN values using math.isnan().

--
nosy: +mark.dickinson

___
Python tracker 

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

[issue35724] Check for main interpreter when checking for "main" thread (for signal handling)

[Eric Snow]

Change by Eric Snow :


--
assignee:  -> eric.snow
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

[issue35724] Check for main interpreter when checking for "main" thread (for signal handling)

[Eric Snow]

Eric Snow  added the comment:


New changeset 64d6cc826dacebc2493b1bb5e8cb97828eb76f81 by Eric Snow in branch 
'master':
bpo-35724: Explicitly require the main interpreter for signal-handling. 
(GH-11530)
https://github.com/python/cpython/commit/64d6cc826dacebc2493b1bb5e8cb97828eb76f81


--

___
Python tracker 

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

[issue36083] Misformated manpage: --check-hash-based-pycs ´default´|´always´|´never´

[Benjamin Peterson]

Benjamin Peterson  added the comment:

A PR would be welcome.

On Sat, Feb 23, 2019, at 12:08, Cheryl Sabella wrote:
> 
> Cheryl Sabella  added the comment:
> 
> Thanks for the report, Miro!  Adding Benjamin Peterson to the nosy, 
> since that was his commit.  I'd wait until he comments before making a 
> PR.
> 
> --
> nosy: +benjamin.peterson, cheryl.sabella
> 
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue36091] clean up async generator from types module

[Henry Chen]

Henry Chen  added the comment:

As it happens @cheryl.sabella has created a very useful data set of which files 
are impacted by open PRs: https://github.com/csabella/pulls

and as of 2019-02-18, the only open PR that relates to Lib/types.py is
https://github.com/python/cpython/pull/5068 on an unrelated matter

--

___
Python tracker 

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

[issue36085] Enable better DLL resolution

[mattip]

mattip  added the comment:

> legitimately modify PATH for process launches

Correct me if I'm wrong, don't process launches use the `env` kwarg for Popen, 
not the raw os.environ['PATH']?

--

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Brandt Bucher]

Brandt Bucher  added the comment:

As a design decision, I consciously chose "no". However, it would be 
straightforward to make the change to support float subclasses:

#define ISNAN(N) (N->ob_type == _Type && Py_IS_NAN(PyFloat_AsDouble(N)))

becomes

#define ISNAN(N) (PyFloat_Check(N) && Py_IS_NAN(PyFloat_AsDouble(N)))

--

___
Python tracker 

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

[issue36090] spelling error in PEP219 introduction

[Cheryl Sabella]

Cheryl Sabella  added the comment:

Yes, 景云鹏, Karthikeyan, or Joannah, please open an issue on the PEPs repo and 
then add the link here and close this issue.  景云鹏, if you're interested in 
submitting a PR, the process is similar on the PEPs repo, so feel free to work 
on this issue there.

Also, there have been some older issues that are for PEPs, but were created 
before there was an issues list to report them on, so if you run into one of 
them while triaging, just do the same.

Thanks!

--
nosy: +cheryl.sabella

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Does it work for subclasses of float? For other floating point types like 
numpy.float32?

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue36094] When using an SMTP SSL connection,, get ValueError.

[Cheryl Sabella]

Cheryl Sabella  added the comment:

tyrone-zhao, thank you for the report and the detail on the commit.

Adding @christian.heimes to the nosylist as he added change this under 
issue19785 and @dstufft as he modified it to be `self._host`.

--
nosy: +cheryl.sabella, christian.heimes, dstufft

___
Python tracker 

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

[issue36083] Misformated manpage: --check-hash-based-pycs ´default´|´always´|´never´

[Cheryl Sabella]

Cheryl Sabella  added the comment:

Thanks for the report, Miro!  Adding Benjamin Peterson to the nosy, since that 
was his commit.  I'd wait until he comments before making a PR.

--
nosy: +benjamin.peterson, cheryl.sabella

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Cheryl Sabella]

Cheryl Sabella  added the comment:

This has been brought up in the past, for example, see #12286.

--
nosy: +cheryl.sabella

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +rhettinger, tim.peters

___
Python tracker 

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

[issue35724] Check for main interpreter when checking for "main" thread (for signal handling)

[Eric Snow]

Change by Eric Snow :


--
pull_requests:  -11124

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Brandt Bucher]

Change by Brandt Bucher :


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

___
Python tracker 

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

[issue36095] Better NaN sorting.

[Brandt Bucher]

New submission from Brandt Bucher :

Sorting sequences containing NaN values produces an incompletely sorted result. 
Further, because of the complexity of the timsort, this incomplete sort often 
silently produces unintuitive, unstable-seeming results that are extremely 
sensitive to the ordering of the inputs:

>>> sorted([3, 1, 2, float('nan'), 2.0, 2, 2.0])
[1, 2, 2.0, 2.0, 3, nan, 2]
>>> sorted(reversed([3, 1, 2, float('nan'), 2.0, 2, 2.0]))
[1, 2.0, 2, 2.0, nan, 2, 3]

The patch I have provided addresses these issues, including for lists 
containing nested lists/tuples with NaN values. Specifically, it stably sorts 
NaNs to the end of the list with no changes to the timsort itself (just the 
element-wise comparison functions):

>>> sorted([3, 1, 2, float('nan'), 2.0, 2, 2.0])
[1, 2, 2.0, 2, 2.0, 3, nan]
>>> sorted([[3], [1], [2], [float('nan')], [2.0], [2], [2.0]])
[[1], [2], [2.0], [2], [2.0], [3], [nan]]

It also includes a new regression test for this behavior.

Some other benefits to this patch:

* These changes generally result in a sorting performance improvement across 
data types. The largest increases here are for nested lists, since we add a new 
unsafe_list_compare function. Other speed increases are due to 
safe_object_compare's delegation to unsafe comparison functions for objects of 
the same type. Specifically, the speed impact (positive is faster, negative is 
slower) is between:

* -3% and +3% (10 elements, no PGO)
* 0% and +4% (10 elements, PGO)
* 0% and +9% (1000 elements, no PGO)
* -1% and +9% (1000 elements, PGO)

* The current weird NaN-sorting behavior is not documented, so this is not a 
breaking change.

* IEEE754 compliance is maintained. The result is still a stable (arguably, 
more stable), nondecreasing ordering of the original list.

--
components: Interpreter Core
messages: 336401
nosy: brandtbucher
priority: normal
severity: normal
status: open
title: Better NaN sorting.
type: behavior
versions: Python 3.8

___
Python tracker 

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

[issue35512] patch.dict resolves in_dict eagerly (should be late resolved)

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


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

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Any objections to getting this patch applied today so that it will be in the 
second alpha?

Of course, further adjustments can still be made afterwards if needed.

--

___
Python tracker 

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

[issue1054041] Python doesn't exit with proper resultcode on SIGINT

[Gregory P. Smith]

Gregory P. Smith  added the comment:


New changeset 06babb24225d41a76e4aee975380294ca1ee1d7c by Gregory P. Smith in 
branch 'master':
bpo-1054041: Add What's New docs. (GH-11999)
https://github.com/python/cpython/commit/06babb24225d41a76e4aee975380294ca1ee1d7c


--

___
Python tracker 

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

[issue36085] Enable better DLL resolution

[Steve Dower]

Steve Dower  added the comment:

> Even better would be official python/Microsoft support for a CLI version of 
> depends.exe like ldd on linux

The dumpbin.exe tool with /IMPORTS is a good start, and I've definitely wrapped 
it in Python before to do this kind of analysis (not reproducibly, yet...).

Doing this kind of analysis live is oddly tough, but there may be an ETW 
provider that a debug hook could enable to get more of a trace. Again, we're 
deep in third-party tool territory, not a change to core CPython.

Certainly if we can drop support for base Windows 7 we will document how to use 
more recent OS support via whatever we add. Though to a certain extent those 
hitting problems are going deep enough that reading the MSDN docs will have to 
be mandatory (at least for those who want to know "why"). I really don't want 
to have to reproduce those docs and make them guaranteed Python semantics.

> will annoy developers whose code base is full of `os.environ['PATH']` games. 
> Perhaps the solution should come with a deprecation warning when setting 
> `os.environ['PATH']`.

Yeah, this is the downside of changing anything at all, though of course since 
resolving DLLs via PATH is already broken, those developers are already annoyed 
;) And we can't add warning that wouldn't annoy those who legitimately modify 
PATH for process launches. So I think it's mostly about providing a supported 
path for those developers to be able to port their code when they discover it's 
broken.

--

___
Python tracker 

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

[issue35886] Move PyInterpreterState into Include/internal/pycore_pystate.h

[Eric Snow]

Change by Eric Snow :


--
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

[issue35886] Move PyInterpreterState into Include/internal/pycore_pystate.h

[Eric Snow]

Eric Snow  added the comment:


New changeset be3b295838547bba267eb08434b418ef0df87ee0 by Eric Snow in branch 
'master':
bpo-35886: Make PyInterpreterState an opaque type in the public API. (GH-11731)
https://github.com/python/cpython/commit/be3b295838547bba267eb08434b418ef0df87ee0


--

___
Python tracker 

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

[issue1054041] Python doesn't exit with proper resultcode on SIGINT

[Gregory P. Smith]

Change by Gregory P. Smith :


--
pull_requests: +12029

___
Python tracker 

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

[issue4502] Allowing get_pre_input_hook from Readline

[Sanyam Khurana]

Sanyam Khurana  added the comment:

I'm working on applying this patch cleanly and writing a test for this.

However, it seems I'm unable to import `readline` in compiled version of 
Python. I'm trying to provide a path to the installation of readline in my 
system using LDFLAGS, and then reconfiguring and recompiling, but seems like it 
didn't work.

Can someone provide me a pointer here, please?

--
assignee:  -> CuriousLearner
nosy: +CuriousLearner
versions: +Python 3.8 -Python 3.3

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

> Side note: I’m the author of the sysv_ipc package you found, as well as the 
> posix_ipc package.

Sorry, I didn't realize it was you.

> Not true.  A manager started by one process can be connected to by another 
> process that is not a child.  This is covered in the docs here:  
> https://docs.python.org/3/library/multiprocessing.html#using-a-remote-manager 

Ah nice! OK then. With this + Philip's explanation on why shmat()/shmdt() are 
not needed I guess I ran out of API-related complaints now. =)

--

___
Python tracker 

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

[issue36094] When using an SMTP SSL connection,, get ValueError.

[SilentGhost]

Change by SilentGhost :


--
stage: patch review -> 
type: resource usage -> behavior
versions: +Python 3.8

___
Python tracker 

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

[issue36094] When using an SMTP SSL connection,, get ValueError.

[SilentGhost]

Change by SilentGhost :


--
stage:  -> patch review

___
Python tracker 

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

[issue35648] Add use_srcentry parameter to shutil.copytree()

[flokX]

flokX  added the comment:

You are right about the bug. The funny thing is, I never saw it.

The problem I see is another.
The use_srcentry variable in the _copytree function is set by determining if 
the copy_function is the function copy2 or copy. If so the srcentry is passed 
to the copy_function. If the user passes a custom copy_function to copytree, 
this function will ever become only the srcname and not the srcentry. To 
summarize it: The integrated copy_functions get the srcentry and custom 
copy_functions get the srcname.
But what is if the custom copy_function is a edited copy2 function or needs the 
srcentry? In order to fix this was my idea to have a parameter to control if 
the custom copy_function get the srcentry or a srcname.
Please write me if there is anything misconception in my thoughts or other 
objections?

--

___
Python tracker 

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

[issue36094] When using an SMTP SSL connection,, get ValueError.

[Roundup Robot]

Change by Roundup Robot :


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

___
Python tracker 

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

[issue36094] When using an SMTP SSL connection,, get ValueError.

[赵军昱]

New submission from 赵军昱 <200612...@qq.com>:

The following bug occurs when you connect after creating an instance of 
SMTP_SSL:
```
import smtplib


smtp_server = "smtp.163.com"
con2 = smtplib.SMTP_SSL()
con2.connect(smtp_server, 465)
```
ValueError:
server_hostname cannot be an empty string or start with a leading dot.
  File "E:\code\noUse.py", line 8, in 
con2.connect(smtp_server, 465)

--
components: email
files: 1.png
messages: 336393
nosy: barry, r.david.murray, tyrone-zhao
priority: normal
severity: normal
status: open
title: When using an SMTP SSL connection,, get ValueError.
type: resource usage
versions: Python 3.7
Added file: https://bugs.python.org/file48167/1.png

___
Python tracker 

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

[issue35648] Add use_srcentry parameter to shutil.copytree()

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

It turns out that's a bug I introduced in PR-7874. I'm providing:
https://github.com/python/cpython/pull/11997
...which fixes it without introducing a new parameter. I also verified that 
monkey patching shutil.copy2 and shutil.copy doesn't cause any issue.

--
nosy: +giampaolo.rodola
pull_requests: +12026
stage: resolved -> patch review

___
Python tracker 

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

[issue35652] Add use_srcentry parameter to shutil.copytree() II

[Giampaolo Rodola']

Change by Giampaolo Rodola' :


--
pull_requests: +12024

___
Python tracker 

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

[issue33695] Have shutil.copytree(), copy() and copystat() use cached scandir() stat()s

[Giampaolo Rodola']

Change by Giampaolo Rodola' :


--
pull_requests: +12025

___
Python tracker 

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

[issue36085] Enable better DLL resolution

[mattip]

mattip  added the comment:

Clear documentation would go a long way toward onboarding package providers. Of 
course this does not solve the problem for packages with no active ongoing 
support for windows, and will annoy developers whose code base is full of 
`os.environ['PATH']` games. Perhaps the solution should come with a deprecation 
warning when setting `os.environ['PATH']`.

It would be very helpful if failure to import a pyd (or for that matter to open 
a DLL with ctypes) due to missing support dlls could be easily debugged. Right 
now we get a message from windows that seems to suggest the file was not found.
- Python could check if the file exists on disk and print a more helpful message
- A debug hook to print the dll search path at the time of the failed 
LoadLibraryEx call, or perhaps adding it as an attribute of the Exception (this 
might be nice to have on Linux as well, even though there the Exception already 
includes the name of the missing *.so).

Even better would be official python/Microsoft support for a CLI version of 
depends.exe like ldd on linux, but that seems much harder and is out of scope 
for this issue.

--
nosy: +mattip

___
Python tracker 

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

[issue35512] patch.dict resolves in_dict eagerly (should be late resolved)

[Mario Corchero]

Mario Corchero  added the comment:

Great, all yours :) I'll be happy to review.

--

___
Python tracker 

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

[issue35512] patch.dict resolves in_dict eagerly (should be late resolved)

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Thanks Mario for the details. I had almost the same patch while writing 
msg336300 :) There were no test case failures except that I had resolved it in 
the constructor storing the string representation as a separate variable and 
also while calling the function which could be avoided as per your approach to 
just store the string and resolve once during function call. I think this is a 
good way to do this. Are you planning to create a PR or shall I go ahead with 
this?

--

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Davin Potts]

Davin Potts  added the comment:

> FWIW I bumped into this lib: http://semanchuk.com/philip/sysv_ipc/

The author of that lib, Philip Semanchuk, is one of the people participating in 
this effort -- he has posted above in msg334934 here on b.p.o. and has helped 
review the PR in GH-11816.

He is also the author of the posix_ipc package which was the original basis for 
our POSIX Shared Memory implementation here.

The decision to base our Unix platform support upon POSIX and not SystemV 
libraries came after considerable research and there are important differences 
between the two.  To oversimplify:  POSIX Shared Memory support has now been 
available for some time on Linux, *BSD, MacOS, and others and is something of a 
successor to the SystemV.


> That assumes a single app/process which spawns a child (the "worker").

Not true.  A manager started by one process can be connected to by another 
process that is not a child.  This is covered in the docs here:  
https://docs.python.org/3/library/multiprocessing.html#using-a-remote-manager  
That child can then request that shared memory blocks it creates be remotely 
tracked and managed by that remote process's manager.  While I would not expect 
this to be a common use case, this is a feature of BaseManager that we inherit 
into SharedMemoryManager.

The SyncManager.Lock can be used as part of this as well.  Thus, two unrelated 
apps/processes *can* coordinate their management of shared memory blocks 
through the SharedMemoryManager.


> That would translate into a new Semaphore(name=None, create=False)
> class which (possibly?) would also provide better performances
> compared to SyncManager.Semaphore

Right!  You might have noticed that Philip has such a semaphore construct in 
his posix_ipc lib.

I opted to not attempt to add this feature as part of this effort to both (1) 
keep focused on the core needs to work with shared memory, and (2) to take more 
time in the future to work out how to get cross-platform support for the 
semaphore right (as you point out, there are complications to work through).


> Extra 1: apparently there are also POSIX msgget(), msgrcv() and
> msgsnd() syscalls which could be used to implement a System-V message
> Queue similar to SyncManager.Queue later on.

Right!  This is also something Philip has in his posix_ipc lib.  This should be 
part of the roadmap for what we do next with SharedMemory.  This one may be 
complicated by the fact that not all platforms that implement POSIX Shared 
Memory chose to also implement these functions in the same way.  We will need 
time to work out what we can or can not reasonably do here.


> Extra 2: given the 2 distinct use-cases I wonder if the low-level
> component (shared_memory.py) really belongs to multiprocessing module

Given what I wrote above about how multiprocessing.managers does enable these 
use cases and the existing "distributed shared memory" support in 
multiprocessing, I think it logically belongs in multiprocessing.  I suggest 
that "shm_open" and "shm_unlink" are our low-level tools, which appropriately 
are in _posixshmem, but SharedMemory and the rest are high-level tools; 
SharedMemoryManager will not be able to cover all life-cycle management use 
cases thus SharedMemory will be needed by many and in contrast, "shm_open" and 
"shm_unlink" will be needed only by those wishing to do something wacky.  
(Note: I am not trying to make "wacky" sound like a bad thing because wacky can 
be very cool sometimes.)


Philip's ears should now be burning, I mentioned him so many times in this 
post.  Ah!  He beat me to it while I was writing this.  Awesome!

We would not be where we are with SharedMemory without his efforts over many 
years with his posix_ipc lib.

--

___
Python tracker 

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

[issue35648] Add use_srcentry parameter to shutil.copytree()

[Giampaolo Rodola']

Change by Giampaolo Rodola' :


--
assignee: docs@python -> 
resolution: later -> 
status: closed -> open

___
Python tracker 

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

[issue35652] Add use_srcentry parameter to shutil.copytree() II

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

Not sure why you created 2 identical issues. Closing this one as a duplicate of 
issue35648.

--
nosy: +giampaolo.rodola
resolution:  -> duplicate
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

[issue35652] Add use_srcentry parameter to shutil.copytree() II

[Giampaolo Rodola']

Change by Giampaolo Rodola' :


--
pull_requests:  -12023

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Philip Semanchuk]

Philip Semanchuk  added the comment:

> On Feb 23, 2019, at 10:40 AM, Giampaolo Rodola'  
> wrote:
> 
> 
> Giampaolo Rodola'  added the comment:
> 
>> We are consciously choosing to not support an atomic "create or attach".  
>> This significantly simplifies the API and avoids the valid concerns raised 
>> around user confusion relating to that behavior (including the use of 
>> different specified 'size' values in a race) but does not preclude our 
>> potentially introducing this as a feature in the future.
> 
> I understand that because of *size* we cannot solve the race condition issue 
> unless the user uses some sort of synchronization mechanism. FWIW I bumped 
> into this lib:
> http://semanchuk.com/philip/sysv_ipc/
> ...which provides two separate APIs to "create" and "attach":
> 
 SharedMemory("name", IPC_CREX)
 attach("name")
> 
> At this point I'm agnostic about the API, which is probably just a matter of 
> personal taste (e.g. one may prefer a separate SharedMemory.attach() 
> classmethod or a *mode* argument accepting "x" and "a"). I see that that lib 
> use shmat() on attach and shmdt() on detach. I'm not sure if that makes a 
> difference, just mentioning it because your implementation doesn't do that on 
> close() and perhaps it should.

attach() and detach() are particular to SysV IPC which is different from the 
POSIX IPC that’s being used here. There’s no need for attach() and detach() 
with POSIX shared memory. 

POSIX IPC is generally simpler than SysV IPC, in part because it was developed 
after SysV IPC so the developers had the benefit of experience with the older 
API.

Side note: I’m the author of the sysv_ipc package you found, as well as the 
posix_ipc package.

--

___
Python tracker 

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

[issue35512] patch.dict resolves in_dict eagerly (should be late resolved)

[Mario Corchero]

Mario Corchero  added the comment:

Interesting, `patch` does resolve it when the patched function is called (see 
https://github.com/python/cpython/blob/175421b58cc97a2555e474f479f30a6c5d2250b0/Lib/unittest/mock.py#L1269)
 vs patch.dict that resolves it at the time the patcher is created - when 
decorating -  (see 
https://github.com/python/cpython/blob/175421b58cc97a2555e474f479f30a6c5d2250b0/Lib/unittest/mock.py#L1624).

An option might be to delay the resolution as done for patch, changing 
https://github.com/python/cpython/blob/175421b58cc97a2555e474f479f30a6c5d2250b0/Lib/unittest/mock.py#L1625
 to `self.in_dict_name = in_dict`

Example untested patch:

```
diff --git a/Lib/unittest/mock.py b/Lib/unittest/mock.py
index 8f46050462..5328fda417 100644
--- a/Lib/unittest/mock.py
+++ b/Lib/unittest/mock.py
@@ -1620,9 +1620,7 @@ class _patch_dict(object):
 """

 def __init__(self, in_dict, values=(), clear=False, **kwargs):
-if isinstance(in_dict, str):
-in_dict = _importer(in_dict)
-self.in_dict = in_dict
+self.in_dict_name = in_dict
 # support any argument supported by dict(...) constructor
 self.values = dict(values)
 self.values.update(kwargs)
@@ -1649,7 +1647,7 @@ class _patch_dict(object):
 attr_value = getattr(klass, attr)
 if (attr.startswith(patch.TEST_PREFIX) and
  hasattr(attr_value, "__call__")):
-decorator = _patch_dict(self.in_dict, self.values, self.clear)
+decorator = _patch_dict(self.in_dict_name, self.values, 
self.clear)
 decorated = decorator(attr_value)
 setattr(klass, attr, decorated)
 return klass
@@ -1662,7 +1660,11 @@ class _patch_dict(object):

 def _patch_dict(self):
 values = self.values
-in_dict = self.in_dict
+if isinstance(self.in_dict_name, str):
+in_dict = _importer(self.in_dict_name)
+else:
+in_dict = self.in_dict_name
+self.in_dict = in_dict
```


> This seems to be not a problem with patch.object where redefining a class 
> later like dict seems to work correctly and maybe it's due to creating a new 
> class itself that updates the local to reference new class?

For patch, when you create a new class, the new one is patched as the name is 
resolved at the time the decorated function is executed, not when it is 
decorated. See:

```
$ cat t.py
from unittest import mock
import c

target = dict(a=1)

@mock.patch("c.A", "target", "updated")
def test_with_decorator():
print(f"target inside decorator : {A.target}")

def test_with_context_manager():
with mock.patch("c.A", "target", "updated"):
print(f"target inside context : {A.target}")

class A:
target = "changed"

c.A = A
test_with_decorator()
test_with_context_manager()
xarmariocj89 at DESKTOP-9B6VH3A in ~/workspace/cpython on master*
$ cat c.py
class A:
target = "original"
mariocj89 at DESKTOP-9B6VH3A in ~/workspace/cpython on master*
$ ./python ./t.py
target inside decorator : changed
target inside context : changed
```

If `patch` was implemented like `patch.dict`, you would see the first as 
"changed" as the reference to `c.A` would have been resolved when the decorator 
was run (before the re-definition of `A`).

About `patch.object`, it cannot be compared, as it grabs the name at the time 
you execute the decorator because you are not passing a string, but the actual 
object to patch.

--

___
Python tracker 

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

[issue35431] Add a function for computing binomial coefficients to the math module

[Yash Aggarwal]

Yash Aggarwal  added the comment:

Can I get a consensus on weather math.perm() is needed?

--

___
Python tracker 

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

[issue35813] shared memory construct to avoid need for serialization between processes

[Giampaolo Rodola']

Giampaolo Rodola'  added the comment:

> We are consciously choosing to not support an atomic "create or attach".  
> This significantly simplifies the API and avoids the valid concerns raised 
> around user confusion relating to that behavior (including the use of 
> different specified 'size' values in a race) but does not preclude our 
> potentially introducing this as a feature in the future.

I understand that because of *size* we cannot solve the race condition issue 
unless the user uses some sort of synchronization mechanism. FWIW I bumped into 
this lib:
http://semanchuk.com/philip/sysv_ipc/
...which provides two separate APIs to "create" and "attach":

>>> SharedMemory("name", IPC_CREX)
>>> attach("name")

At this point I'm agnostic about the API, which is probably just a matter of 
personal taste (e.g. one may prefer a separate SharedMemory.attach() 
classmethod or a *mode* argument accepting "x" and "a"). I see that that lib 
use shmat() on attach and shmdt() on detach. I'm not sure if that makes a 
difference, just mentioning it because your implementation doesn't do that on 
close() and perhaps it should.


> Combined with a SyncManager.Lock, users can already achieve an atomic "create 
> or attach" using this simpler API.

That assumes a single app/process which spawns a child (the "worker"). In that 
case SyncManager.Lock/others is indeed compatible with SharedMemory and can be 
used to implement non-racy "create or attach" and also to synchronize memory 
access on read and write. But AFAICT there are two uses cases for this 
functionality, and there currently is no mechanism to do any that if you have 
two unrelated apps/processes relying on a common shared memory *name* and 
*size*. I'm taking a peek at "man smh_overview" which says:

<>

That would translate into a new Semaphore(name=None, create=False) class which 
(possibly?) would also provide better performances compared to 
SyncManager.Semaphore. Not sure if we can do the same on Windows though. 

Extra 1: apparently there are also POSIX msgget(), msgrcv() and msgsnd() 
syscalls which could be used to implement a System-V message Queue similar to 
SyncManager.Queue later on. 

Extra 2: given the 2 distinct use-cases I wonder if the low-level component 
(shared_memory.py) really belongs to multiprocessing module. Perhaps this 
should be provided as a separate "sharedmemory" module with 
multiprocessing.managers.SharedMemoryMemory being the high-level interface.

--

___
Python tracker 

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

[issue35652] Add use_srcentry parameter to shutil.copytree() II

[Giampaolo Rodola']

Change by Giampaolo Rodola' :


--
pull_requests: +12023

___
Python tracker 

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

[issue33695] Have shutil.copytree(), copy() and copystat() use cached scandir() stat()s

[flokX]

Change by flokX :


--
pull_requests: +12022

___
Python tracker 

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

[issue36090] spelling error in PEP219 introduction

[Joannah Nanjekye]

Joannah Nanjekye  added the comment:

xtreak, I agree. I think the best way to report an issue on a PEP is on the 
github repository for PEPs.

Feel free to open an issue here : https://github.com/python/peps/issues.

--
nosy: +nanjekyejoannah

___
Python tracker 

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

[issue34656] [CVE-2018-20406] memory exhaustion in Modules/_pickle.c:1393

[dfmz77669]

dfmz77669  added the comment:

In python2, Picklertype donot has tp init which has bug in python3 Pickler_Type.
I think it not effect python2.
Can you arch more infor?
thanks

--
components: +ctypes -FreeBSD
nosy: +dfmz77669
versions:  -Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

___
Python tracker 

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