[issue34580] sqlite doc: clarify the scope of the context manager

[Daniel Jakots]

Daniel Jakots  added the comment:

Thanks, I lacked the greater picture.

Yes, adding a "con.close()" line to the snippet would clarify for me!

--

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Thanks for the comments. I will add `con.close()` to the examples linked.
Should I remove or change this line as per Daniel's comment "Note that this
does not automatically call :meth:`close` on the connection object."

Thanks
-- 

Regards,
Karthikeyan S

--

___
Python tracker 

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

[issue31734] crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized

[Berker Peksag]

Change by Berker Peksag :


--
resolution:  -> wont fix
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

[issue34612] doc Some classes are treated as functions in Built-in Functions

[Andrés Delfino]

New submission from Andrés Delfino :

Beyond other classes documented as functions (classmethod, enumerate, filter, 
map, reversed, staticmethod, super and zip), the following issues exist:

* memoryview, range, and tuple are marked as functions
* complex and object treat themselves as functions in their descriptions

Attached PR fixes this.

--
assignee: docs@python
components: Documentation
messages: 324864
nosy: adelfino, docs@python
priority: normal
severity: normal
status: open
title: doc Some classes are treated as functions in Built-in Functions
type: enhancement
versions: Python 2.7, 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

[issue34608] gc.get_referrers behavior change 3.6 to 3.7

[Xiang Zhang]

Change by Xiang Zhang :


--
nosy: +inada.naoki, pitrou

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Berker Peksag]

Berker Peksag  added the comment:

We always explicitly document what the context manager does even if it simply 
calls an object's close() method. See 
https://docs.python.org/3/library/fileinput.html#fileinput.input and 
https://docs.python.org/3/library/shelve.html#shelve.Shelf for example.

In this case, the documentation already explains what the context manager does 
after the with block finishes (it also explains the behavior on success and 
error) with a detailed example.

Would adding a "con.close()" line to the example at 
https://docs.python.org/3/library/sqlite3.html#using-the-connection-as-a-context-manager
 clarify the behavior for you?

--
versions: +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

[issue34605] Avoid master/slave terminology

[Stefan Krah]

Stefan Krah  added the comment:

Trying to remove myself from the nosy list again (I know that the interface 
sometimes surprisingly adds/removes persons).

--

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Berker Peksag]

Berker Peksag  added the comment:

PR 9079 looks good to me.

I think we can use this as an opportunity to make the rest of the examples in 
the sqlite3 documentation more consistent and add missing "conn.close()" calls.

--

___
Python tracker 

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

[issue34588] traceback formatting can drop a frame

[Benjamin Peterson]

Benjamin Peterson  added the comment:

It actually does save space because each traceback entry is usually two lines 
(frame id and source snippet).

I don't really have an opinion about what should happen be printed on the 
boundary cases. My current PR seems like a strict improvement to the current 
implementation, which is just incorrect.

--

___
Python tracker 

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

[issue14156] argparse.FileType for '-' doesn't work for a mode of 'rb'

[Leo Singer]

Leo Singer  added the comment:

I just hit this bug. Would the proposed patch get any more attention if 
submitted as a pull request?

--
nosy: +Leo Singer

___
Python tracker 

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

[issue31652] make install fails: no module _ctypes

[David Spahn]

David Spahn  added the comment:

I'm getting the same error   File 
"/usr/src/Python-3.7.0/Lib/ctypes/__init__.py", line 7, in 
from _ctypes import Union, Structure, Array
ModuleNotFoundError: No module named '_ctypes'
Makefile:1122: recipe for target 'install' failed
make: *** [install] Error 1
 
Linux Mint 19

--
nosy: +dgspahn
Added file: https://bugs.python.org/file47793/query.csv

___
Python tracker 

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

[issue34421] Cannot install package with unicode module names on Windows

[Éric Araujo]

Change by Éric Araujo :


--
assignee:  -> eric.araujo
resolution:  -> fixed
stage: patch review -> commit review
status: open -> pending
type: crash -> behavior
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

[issue34421] Cannot install package with unicode module names on Windows

[miss-islington]

miss-islington  added the comment:


New changeset 77b92b15a5e5c84b91d3fd9d02f63db432fa8903 by Miss Islington (bot) 
in branch '3.7':
bpo-34421 avoid unicode error in distutils logging (GH-8799)
https://github.com/python/cpython/commit/77b92b15a5e5c84b91d3fd9d02f63db432fa8903


--

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Stefan Krah]

Change by Stefan Krah :


--
nosy:  -skrah

___
Python tracker 

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

[issue20178] Derby #9: Convert 52 sites to Argument Clinic across 11 files

[Berker Peksag]

Berker Peksag  added the comment:

I'm working on converting Modules/_sqlite/* to Argument Clinic.

--
nosy: +berker.peksag
versions: +Python 3.8 -Python 3.5

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Daniel Jakots]

Daniel Jakots  added the comment:

Yes, I would totally support this move as it would show users that it's 
important to close it!

--

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Matej Cepl]

Change by Matej Cepl :


--
nosy:  -mcepl

___
Python tracker 

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

[issue34596] [unittest] raise error if @skip is used with an argument that looks like a test method

[Zachary Ware]

Zachary Ware  added the comment:

I don't agree that this change makes the implementation significantly more 
cumbersome.  I also think there's a backward compatibility argument to be made 
for allowing the uncalled usage, particularly considering the OP's published 
example and other similar ones, such as 
https://stackoverflow.com/questions/2066508/disable-individual-python-unit-tests-temporarily
 which was for me the first Google result for "python unittest skip" that was 
not our own docs.

--

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Thanks, I have pushed a change adding `con.close` at the end of the example and 
also verified that `./python.exe Doc/includes/sqlite3/ctx_manager.py` works as 
expected.

Thanks

--

___
Python tracker 

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

[issue34546] Add encryption support to zipfile

[大野隆弘]

大野隆弘  added the comment:

My original reason of this is supporting Windows Explore decryption.
That doesn't support AES but support only this traditional PKWARE
encryption.
In my work, some recipients who received the zip file cannot install 3rd
party tools on their Windows
https://blogs.msdn.microsoft.com/oldnewthing/20180515-00/?p=98755

But as Christian explained for me in below thread, I understand we should
use 3rd party module for this purpose
https://mail.python.org/pipermail/python-dev/2018-September/155091.html

Thanks and Regards,
---
Takahiro Ono

2018年9月8日(土) 6:34 Serhiy Storchaka :

>
> Change by Serhiy Storchaka :
>
>
> --
> resolution:  -> rejected
> stage: patch review -> resolved
> status: open -> closed
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Berker Peksag]

Berker Peksag  added the comment:

Personally, I find parent/child more descriptive if it can be used in the same 
context with master/slave, so I'm in favor of replacing master/slave with 
parent/child where applicable.

However, I agree that the code changes in PR 9100 are a bit excessive. It would 
be nice if we could keep the members of the public API (some of them have 
already been deprecated) and variable/function/parameter names left out of this 
cleanup.

--
components: +Documentation
nosy: +berker.peksag
type:  -> enhancement

___
Python tracker 

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

[issue34421] Cannot install package with unicode module names on Windows

[miss-islington]

Change by miss-islington :


--
pull_requests: +8570

___
Python tracker 

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

[issue34421] Cannot install package with unicode module names on Windows

[Éric Araujo]

Éric Araujo  added the comment:


New changeset 0afada163c7ef25c3a9d46ed445481fb69f2ecaf by Éric Araujo (Julien 
Malard) in branch 'master':
bpo-34421 avoid unicode error in distutils logging (GH-8799)
https://github.com/python/cpython/commit/0afada163c7ef25c3a9d46ed445481fb69f2ecaf


--

___
Python tracker 

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

[issue34421] Cannot install package with unicode module names on Windows

[miss-islington]

Change by miss-islington :


--
pull_requests: +8571

___
Python tracker 

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

[issue34612] doc Some classes are treated as functions in Built-in Functions

[Eric V. Smith]

Eric V. Smith  added the comment:

I'm not sure this is an improvement. While it's true that 'complex' is a class, 
it's described here as a function. Same as 'int'. The fact that it's a function 
or class isn't so important here.

I suspect it will confuse people to have something described as a class in the 
section titled 'Built-in Functions'. We wouldn't want to change the section to 
the more correct 'Built-in Callables'.

--
nosy: +eric.smith

___
Python tracker 

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

[issue34612] doc Some classes are treated as functions in Built-in Functions

[Andrés Delfino]

Andrés Delfino  added the comment:

Please note that several classes are marked as such (e.g., int, float, str, 
dict, list) and bool for example treats itself as a class in it's description.

Perhaps your concerns applies to all those ocurrences too?

--

___
Python tracker 

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

[issue34612] doc Some classes are treated as functions in Built-in Functions

[Raymond Hettinger]

Raymond Hettinger  added the comment:

I concur with Eric.  These were marked as functions in the function section of 
the docs.  Their role as classes is noted in the body.  And their role as 
complete classes with a listing of their methods is documented elsewhere.

--
nosy: +rhettinger
resolution:  -> rejected
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

[issue34611] some examples in 'itertools' modules docs are inaccuracy.

[taketakeyyy]

Change by taketakeyyy :


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

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Berker Peksag]

Berker Peksag  added the comment:

> Should I remove or change this line as per Daniel's comment "Note that
> this does not automatically call :meth:`close` on the connection object."

I'd prefer to keep the current wording as-is.

--

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Sounds good to me too since I copy paste from there time to time and also an 
unclosed connection doesn't seem to trigger a ResourceWarning it seems. I have 
pushed a commit to the same PR. I have changed it manually for all the include 
files. I have ran the files after the PR with the below and I couldn't see any 
breakages. Let me know if I have missed anything in the include files. I guess 
there are some more examples in sqlite3.rst but I don't know if it needs to be 
added on all snippets since they are more focused on the particular function 
unlike the files in the include folder that has full programs.

Verified with : 

$ ls -1 Doc/includes/sqlite3/*py > sample.txt
$ cat sample.txt | xargs -n 1 ./python.exe

Thanks

--

___
Python tracker 

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

[issue34421] Cannot install package with unicode module names on Windows

[miss-islington]

miss-islington  added the comment:


New changeset 3b36642924a51e6bceb7033916c3049764817166 by Miss Islington (bot) 
in branch '3.6':
bpo-34421 avoid unicode error in distutils logging (GH-8799)
https://github.com/python/cpython/commit/3b36642924a51e6bceb7033916c3049764817166


--
nosy: +miss-islington
status: pending -> open

___
Python tracker 

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

[issue34612] doc Some classes are treated as functions in Built-in Functions

[Andrés Delfino]

Change by Andrés Delfino :


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

___
Python tracker 

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

[issue28879] smtplib send_message should add Date header if it is missing, per RFC5322

[Jens Troeger]

Jens Troeger  added the comment:

Any updates on this? Looks like the proposed change has not been merged into 
mainstream yet?

I’m having problems with Google rejecting emails:

(555, b'5.5.2 Syntax error, goodbye. r10-v6sm7321838qtj.41 - gsmtp', '…')

and using IETF’s message linter (https://tools.ietf.org/tools/msglint/) I get 
the following:

ERROR: missing mandatory header 'date' lines 1-7
ERROR: missing mandatory header 'return-path' lines 1-7

amongst a few others.

--
nosy: +_savage

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Mostly, I don't think these changes should be made, particularly in cases where 
"slave" isn't mentioned at all.  The word "master" is used in many contexts 
where master/slave doesn't apply (such as "master key").   Also, I think the PR 
disrespects all the original authors of the various documentation entries, none 
of whom have been consulted.

If a particular passage is demonstrably unclear or offensive, it should be 
changed; otherwise, we shouldn't let vaguely formed notions of political 
correctness shape other clear uses of plain English.  

As far as I can't tell there isn't a single instance where the docs use 
"master" as a reference to human slavery or where the use could be seen to 
imply an endorsement of that notion.

FWIW, Guido drew a line for this a few years ago when someone suggested 
removing the example using the phrase, "I see said the blind man and he picked 
up the hammer and saw".  The judgment was that we weren't going to go down this 
path unless there was actual offensive speech.

--
nosy: +rhettinger

___
Python tracker 

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

[issue34611] some examples in 'itertools' modules docs are inaccuracy.

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

I don't know if it's worth it to edit the results to return Python data 
structures in the linked PR. The current version is more concise and indicates 
the general result of the function instead of the actual return values of the 
function calls which is intentional. Maybe is there some example in itertools 
that you are referring to that has incorrect results?

Thanks

--
nosy: +xtreak

___
Python tracker 

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

[issue34612] doc Some classes are treated as functions in Built-in Functions

[Eric V. Smith]

Eric V. Smith  added the comment:

Ah, you're correct. I just looked for the word "class" inside the "int" text, 
and it doesn't appear there: I thought it was deliberately left out. But it 
does show up in the sub-section header (before "int" itself). Sorry about that.

The text changes look good, then. I don't know enough about Sphinx to know how 
changing the meta-data affects things.

--

___
Python tracker 

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

[issue34608] gc.get_referrers behavior change 3.6 to 3.7

[Benjamin Peterson]

Benjamin Peterson  added the comment:

Likely fallout from 5a625d0aa6a6d9ec6574ee8344b41d63dcb9897e.

get_referrers() doesn't really guarantee anything. It's more of a clever hack 
based on however the Python GC works at the moment. So, this it probably 
WONTFIX.

--
nosy: +benjamin.peterson

___
Python tracker 

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

[issue34611] some examples in 'itertools' modules docs are inaccuracy.

[taketakeyyy]

Change by taketakeyyy :


--
assignee: docs@python
components: Documentation
nosy: docs@python, taketake...@gmail.com
priority: normal
severity: normal
status: open
title: some examples in 'itertools' modules docs are inaccuracy.
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

[issue34611] some examples in 'itertools' modules docs are inaccuracy.

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
assignee: docs@python -> rhettinger
nosy: +rhettinger

___
Python tracker 

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

[issue34595] PyUnicode_FromFormat(): add %T format for an object type name

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

I think we need to handle only two cases: short and fully qualified names. 
__qualname__ without __module__ doesn't make sense, and the value of tp_name 
depends on implementation details (is it Python class or builtin class, heap 
class or dynamic class?). Maybe use %t and %T?

But we may want to support formatting the name of the type itself and the name 
of the object's type. This give us 4 variants.

For old string formatting we can introduce new % codes (with possible 
modifiers). But in modern string formatting "T" can have meaning for some types 
(e.g. for datetime). We can implement __format__ for the type type itself 
(though it can cause confusion if cls.__format__() is different from 
cls.__format__(instance)), but for formatting the name of  the object's type 
(as in your original proposition) we need to add a new  conversion flag like 
"!r".

--

___
Python tracker 

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

[issue23855] Missing Sanity Check for malloc() in PC/_msi.c

[miss-islington]

Change by miss-islington :


--
pull_requests: +8569

___
Python tracker 

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

[issue23855] Missing Sanity Check for malloc() in PC/_msi.c

[miss-islington]

Change by miss-islington :


--
pull_requests: +8568

___
Python tracker 

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

[issue22807] uuid.uuid1() should use uuid_generate_time_safe() if available

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

This breaks pickle compatibility. UUIDs pickled in 3.7 can't be unpickled in 
older Python versions because they do not have the SafeUUID class. See 
issue30977 for possible solution.

--
nosy: +serhiy.storchaka, taleinat

___
Python tracker 

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

[issue34611] some examples in 'itertools' modules docs are inaccuracy.

[Mark Dickinson]

New submission from Mark Dickinson :

@taketakeyyy: Did you mean to include information about *which* examples are 
inaccurate? This issue isn't really useful without that information.

--
nosy: +mark.dickinson

___
Python tracker 

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

[issue34604] Possible mojibake in pwd.getpwnam and grp.getgrnam

[William Grzybowski]

William Grzybowski  added the comment:

What is the policy to amend a new commit to master for %R? Create a new PR? 
Wont that cause problem with NEWS entry?

--

___
Python tracker 

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

[issue20104] expose posix_spawn(p)

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset d700f97b627989d41cd4629dc02969f9a6b56d2f by Serhiy Storchaka in 
branch 'master':
bpo-20104: Change the file_actions parameter of os.posix_spawn(). (GH-6725)
https://github.com/python/cpython/commit/d700f97b627989d41cd4629dc02969f9a6b56d2f


--

___
Python tracker 

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

[issue20104] expose posix_spawn(p)

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Thank you for your contribution Pablo. This issue have appeared much more 
complex and less obvious than it looked initially.

--

___
Python tracker 

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

[issue34586] collections.ChainMap should have a get_where method

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

I concur with Raymond. The purpose of ChainMap is providing a mapping that 
hides the implementation detail of using several mappings as fallbacks. If you 
don't want to hide the implementation detail, you don't need to use ChainMap.

ChainMap exposes underlying mappings as the maps attribute, so you can use this 
implementation detail if you know that it is a ChainMap an not a general 
mapping. It is easy to write a code for searching what mapping contains the 
specified key.

for m in cm.maps:
if key in m:
found = m
break
else:
# raise an error or set a default,
# what is appropriate for your concrete case

or even

found = next(m for m in cm.maps if key in m)

if the key is always found or StopIteration is appropriate.

I don't think that such trivial snatch of code is worth adding a special 
ChainMap method or even documenting it explicitly in the ChainMap documentation.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue34600] python3 regression ElementTree.iterparse() unable to capture comments

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

> But the C version XMLParser requires that its TreeBuilder not be a subclass, 
> when used in iterparse.

Creating a TreeBuilder subclass looks the Right Way. What are problems with 
this? Could you please provide a complete script that works in 2.7, but doesn't 
work in 3.x?

--
nosy: +eli.bendersky, scoder, serhiy.storchaka

___
Python tracker 

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

[issue34596] [unittest] raise error if @skip is used with an argument that looks like a test method

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

It doesn't look like a good design to me if allow a function be a decorator and 
a decorator fabric at the same time. It always lead to cumbersome and 
errorprone implementation. Currently there is only one example of such design 
in the stdlib, other propositions were rejected.

Checking that the argument is a string and raising exception otherwise looks 
good to me for 3.8. There is no a bug that need to be fixed in maintained 
versions. If you use unittest.skip() improperly, it is your failure. Helping to 
catch such mistakes is a new feature.

--
nosy: +serhiy.storchaka
type: behavior -> enhancement
versions:  -Python 2.7, 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

[issue34600] python3 regression ElementTree.iterparse() unable to capture comments

[Stefan Behnel]

Stefan Behnel  added the comment:

There are dedicated handler methods that you can implement: "def comment(self, 
comment)" and "def pi(self, target, data)". Both (c)ElementTree and lxml 
support those.

I think the "target" argument to the parser is a bit underdocumented, and the 
standard TreeBuilder does not implement those methods (because it does not use 
them).

https://docs.python.org/3/library/xml.etree.elementtree.html#xmlparser-objects

Probably worth mentioning that in the docs.

--

___
Python tracker 

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

[issue34574] OrderedDict iterators are exhausted during pickling

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
assignee:  -> serhiy.storchaka
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
assignee: docs@python -> berker.peksag
nosy: +berker.peksag, ghaering

___
Python tracker 

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

[issue34610] Incorrect iteration of Manager.dict() method of the multiprocessing module.

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

DictProxy needs to provide the __iter__() method. And perhaps methods keys(), 
values() and items() need to be reworked in Python 3. has_key() is unneeded in 
Python 3.

It is worth to test also other special and new in Python 3 methods.

--
nosy: +benjamin.peterson, serhiy.storchaka
versions: +Python 2.7, 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

[issue34605] Avoid master/slave terminology

[Gabriel Marko]

Gabriel Marko  added the comment:

@vstinner:

> For diversity reasons, it would be nice to try to avoid "master" and "slave" 
> terminology which can be associated to slavery.

This is too vague. Define what "diversity reasons" are and elaborate your 
point. Referring to some online discussions is not a way for making a serious 
argument. Make a point at least (i.e. define the term, add pro/contra arguments 
and explain why you've taken your decision). Your political standpoint is your 
political standpoint and it's not my business. However, making these changes 
without giving reasons and arguments for them is a problem.

Let me ask:

Are these "diversity reasons" really reasons? What I've heard seen so far 
regarding "diversity reasons, ..." had little to nothing to do with rational 
thinking or argumentation. Is it really necessary to pollute Python code base 
with SJW ideology/terminology? What comes next?

Ad absurdum: If I find anything associated with something unpleasant to me in 
Python code or something which can be considered as e.g. "cultural 
appropriation", I'm free to change it for diversity reason?

--
nosy: +suic

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Matej Cepl]

Matej Cepl  added the comment:

Guys, really, don't we have anything better to do with your time than this 
silliness?

Even if the terminology would be used in the strictest and most brutal meaning, 
i.e., slave must mindlessly follow orders of its master, there is nothing of 
approval of the real human slavery in the past (or present). This is just the 
pretty good terminology for such one-sided relationship which is traditionally 
used in the computer world. By elimination of the word from the world, not a 
yota changes about the reality of slavery in the past (or present).

-1 from me with the extreme violence for introducing such quasi-political 
nonsense to BPO and wasting everybody's time.

--
nosy: +mcepl

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Gabriel Marko]

Gabriel Marko  added the comment:

@mcepl: I completely agree with you that we shouldn't waste time with this. I 
would be better not to dig into the discussion about "master-slave" 
terminology. IMO we don't even need to go into that as the problem here is more 
substantial:

This case can create a very problematic precedent i.e. _on can modify (even 
drastically) a well established terminology based on "pseudo-reasons", 
political opinion or ideology_.

IMO this should be stopped and  prevented as soon as possible for all sake. On 
the other hand, I believe the @vstinner is a rational person and he is able to 
give _rational reasons_ for his decision which other could challenge as 
"potential offensiveness" of language is not an argument.

--

___
Python tracker 

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

[issue34597] Python needs to check existence of functions at runtime for targeting older macOS platforms

[Christoph Reiter]

Christoph Reiter  added the comment:

related: issue31359

--
nosy: +lazka

___
Python tracker 

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

[issue34610] Incorrect iteration of Manager.dict() method of the multiprocessing module.

[Serhiy Storchaka]

Change by Serhiy Storchaka :


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

___
Python tracker 

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

[issue34588] traceback formatting can drop a frame

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

In case of 4 repeated lines it doesn't make much sense to output 3 repeated 
lines and replace the forth line with "Previous line repeated 1 more time". 
This doesn't save space and doesn't help reading the traceback. I think it is 
better to output the forth repeated line.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue34595] PyUnicode_FromFormat(): add %T format for an object type name

[STINNER Victor]

STINNER Victor  added the comment:

An alternative would be to add multiple formatters. Example:

* %Tn: type name, type.__name__, Py_TYPE(obj)->tp_name
* %Tq: qualified name, type.__qualname__
* %Ts: short name, never contains "."
* %Tf: fully qualified name, "module.qualified.name"

What do you think Serhiy?

--

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Eric V. Smith]

Change by Eric V. Smith :


--
nosy: +eric.smith

___
Python tracker 

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

[issue34602] python3 resource.setrlimit strange behaviour under macOS

[marche147]

marche147  added the comment:

Thanks for the repro! It did help for pinpointing the issue.

So I took a little spare time and dived into xnu kernel code, here is my 
assumption based on what I found (N.B. : My assumption comes from a simple 
experiment and a brief skim of the source code within 15 minutes or less, it 
could be seriously wrong since I'm not an expert of XNU kernel, and I currently 
don't have the time to build and debug it.) :

In bsd/kern/kern_resource.c, there's a function `dosetrlimit` which handles the 
`setrlimit` request, and here's part of it:

```
  case RLIMIT_STACK:
// ...
if (limp->rlim_cur > alimp->rlim_cur) {
  user_addr_t addr;
  user_size_t size;

/* grow stack */
size = round_page_64(limp->rlim_cur);
size -= round_page_64(alimp->rlim_cur);

  addr = p->user_stack - round_page_64(limp->rlim_cur);
  kr = mach_vm_protect(current_map(),
   addr, size,
   FALSE, VM_PROT_DEFAULT);
  if (kr != KERN_SUCCESS) {
error =  EINVAL;
goto out;
  }
} // ...

```

As we can see, the kernel will try to `mprotect` the memory preceding the stack 
to `VM_PROT_DEFAULT` (presumably read & write). I then used `vmmap` to see the 
difference between two binaries compiled with different commands. And the 
results are : 

1. Binary compiled without default stack size:

```
- Before calling setrlimit

...
STACK GUARD7ffee76d9000-7ffeeaed9000 [ 56.0M 0K 0K  
   0K] ---/rwx SM=NUL  stack guard for thread 0
...
Stack  7ffeeaed9000-7ffeeb6d9000 [ 8192K20K20K  
   0K] rw-/rwx SM=PRV  thread 0
...
VIRTUAL RESIDENTDIRTY  SWAPPED VOLATILE   
NONVOLEMPTY   REGION
REGION TYPESIZE SIZE SIZE SIZE SIZE 
SIZE SIZECOUNT (non-coalesced)
=== === =  ===    
===  ===
Kernel Alloc Once8K   4K   4K   0K   0K 
  0K   0K2
MALLOC guard page   16K   0K   0K   0K   0K 
  0K   0K5
MALLOC metadata 60K  60K  60K   0K   0K 
  0K   0K6
MALLOC_SMALL  16.0M  16K  16K   0K   0K 
  0K   0K3 see MALLOC ZONE table below
MALLOC_TINY   2048K  32K  32K   0K   0K 
  0K   0K3 see MALLOC ZONE table below
STACK GUARD   56.0M   0K   0K   0K   0K 
  0K   0K2
Stack 8192K  20K  20K   0K   0K 
  0K   0K2
__DATA2324K1192K 208K   0K   0K 
  0K   0K   43
__LINKEDIT   192.7M21.7M   0K   0K   0K 
  0K   0K4
__TEXT9448K8224K   0K   0K   0K 
  0K   0K   48
shared memory8K   8K   8K   0K   0K 
  0K   0K3
=== === =  ===    
===  ===
TOTAL286.3M31.0M 348K   0K   0K 
  0K   0K  110
...

- After calling setrlimit

...
STACK GUARD7ffee76d9000-7ffee76da000 [4K 0K 0K  
   0K] ---/rwx SM=NUL  stack guard for thread 0
...
Stack  7ffee76da000-7ffeeaed9000 [ 56.0M 0K 0K  
   0K] rw-/rwx SM=NUL  thread 0
Stack  7ffeeaed9000-7ffeeb6d9000 [ 8192K20K20K  
   0K] rw-/rwx SM=PRV  thread 0
...
VIRTUAL RESIDENTDIRTY  SWAPPED VOLATILE   
NONVOLEMPTY   REGION
REGION TYPESIZE SIZE SIZE SIZE SIZE 
SIZE SIZECOUNT (non-coalesced)
=== === =  ===    
===  ===
Kernel Alloc Once8K   4K   4K   0K   0K 
  0K   0K2
MALLOC guard page   16K   0K   0K   0K   0K 
  0K   0K5
MALLOC metadata 60K  60K  60K   0K   0K 
  0K   0K6
MALLOC_SMALL  16.0M  20K  20K   0K   0K 
  0K   0K3 see MALLOC ZONE table below
MALLOC_TINY   2048K  32K  32K   0K   0K 
  0K   0K3 see MALLOC ZONE table below
STACK GUARD  4K   0K   0K   0K   0K 
  0K   0K2
Stack 64.0M  20K  20K   0K   0K 
  0K   0K   

[issue34610] Incorrect iteration of Manager.dict() method of the multiprocessing module.

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
nosy: +davin, pitrou

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Cheryl Sabella]

Cheryl Sabella  added the comment:

This is certainly a topic that generates a lot of opinions both ways, not just 
here, but on many other projects.  Based on that, I don't think it's fair to 
blame Victor for bringing it up for discussion.  This is and has been an 
industry discussion for many years (master/slave as it relates to technology 
was named the most politically incorrect term in 2004).  Victor simply brought 
it up here.

All of the same arguments and counterarguments have been mentioned in these 
past discussions.  You can argue that this is ridiculous and political 
correctness has gone too far.  You can argue that this term (master/slave) 
perfectly reflects the model.  You can argue that it's not the same 
relationship as parent/child.  These are probably all valid reasons to not 
change it.  But, I think it's mostly because it's what we're used to.  

Here's an idea -- find a friend and explain to them that there is a concept in 
computer science where there is a group of 'things' and exactly one of those 
things is the main point of contact or first in line, but the other things 
around it that either get direction from that main one, or they are exact 
copies of that main one, or they are downstream from that main one.  Sometimes 
it's because if the main one isn't available, then one of the others is ready 
to take its place.  Or sometimes it's for other purposes (like IDE).  Really 
set the stage in describing what it is.  Then tell them it's called 
master/slave.  They probably won't believe that name because it's a little 
shocking.  We take it for granted, but it doesn't really describe the situation.

I know I'm simplifying and I'm probably not 100% accurate, but I think you get 
my point.  Except for the fact that it's imbedded in engineering and computer 
science and we know it, there's not really a  reason for it to be called what 
it is and there might be other alternatives that are better descriptors.

Personally, one that I've never seen suggested, but one that I think can be 
used to describe the relationship of "one in charge and others follow, but can 
take over" would be alpha/omega (as in a wolf pack).  It's a little stronger 
that leader/follower, doesn't imply the same structure as parent/child, and 
allows for the idea that an omega could take over the role of an alpha.  Plus, 
it's very neutral.  Just too bad the guys who originally coined the phrase 
"master/slave" didn't use "alpha/omega".  

(for the record, political correctness sometimes drives me crazy and I may not 
see a need to change something like master/slave, but at the same time, I can 
understand why other people would like to see it changed)

(second aside - I don't recall that there were arguments a few months ago on 
the PR to make the docs gender neutral.  Maybe people were against that too as 
being 'too politically correct', but they didn't feel the need to talk about.  
To me, this issue is similar to that one.)

--
nosy: +cheryl.sabella

___
Python tracker 

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

[issue34410] itertools.tee not thread-safe; can segfault interpreter when wrapped iterator releases GIL

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

I take this.

--
assignee:  -> serhiy.storchaka
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Ammar Askar]

Ammar Askar  added the comment:

Most of the opposition seems to be against a blanket replacing of all master 
and slave usages, which seems fairly reasonable to me. 

For example, I'm all for the libregrtest change since it conveys the meaning 
just as well and is an internal tool. However, changing MemoryView and pty seem 
way more iffy. These changes are potentially backwards incompatible and 
actually hurt usability.

Unlike other projects, Python doesn't have nearly enough uses of this 
terminology to warrant a massive political discussion in my opinion. Just look 
at the usages on a case-by-case basis and be done with it.

--

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Stefan Krah]

Change by Stefan Krah :


--
nosy:  -skrah

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Stefan Krah]

Stefan Krah  added the comment:

I commented here to explain the master <-> view terminology of memoryview. 
If anyone wants to change that, please open a separate issue and add me as 
the author to the nosy list.

--

___
Python tracker 

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

[issue34586] collections.ChainMap should have a get_where method

[Zahari Dim]

Zahari Dim  added the comment:

On Sat, Sep 8, 2018 at 1:15 PM Serhiy Storchaka  wrote:
>
>
> Serhiy Storchaka  added the comment:
>
> I concur with Raymond. The purpose of ChainMap is providing a mapping that 
> hides the implementation detail of using several mappings as fallbacks. If 
> you don't want to hide the implementation detail, you don't need to use 
> ChainMap.
>
> ChainMap exposes underlying mappings as the maps attribute, so you can use 
> this implementation detail if you know that it is a ChainMap an not a general 
> mapping. It is easy to write a code for searching what mapping contains the 
> specified key.

I don't know where the idea that the underlying mappings are an
implementation detail comes from. It certainly isn't from the
documentation, which mentions uses such as nested scopes and
templates, which cannot be attained with a single mapping. It also
doesn't match my personal usage, where as discussed, even the simpler
cases benefit from information on the underlying mappings. It is a
surprising claim to make given than the entirety of the public
interface specific to ChainMap (maps, new_child and parents) deals
with the fact that there is more structure than one mapping. I also
have a hard time discerning this idea from Raymond's messages.

>
> for m in cm.maps:
> if key in m:
> found = m
> break
> else:
> # raise an error or set a default,
> # what is appropriate for your concrete case

This "trivial snatch of code" contains at least two issues that make
it fail in situations where the actual implementation of `__getitem__`
would work, opening the door for hard to diagnose corner cases. If
anything, in my opinion, the fact that this code is being proposed as
an alternative reinforces the idea that the implementation of the
searching method should be in the standard library.

--

___
Python tracker 

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

[issue34605] Avoid master/slave terminology

[Gabriel Marko]

Gabriel Marko  added the comment:

@cheryl.sabella let me challenge some points in your arguments:

> Based on that, I don't think it's fair to blame Victor for bringing it up for 
> discussion.

Ok, but where was the discussion? @vstinner didn't even make a point and some 
of the PRs were merged. Maybe I'm too spoiled by the field where I come from 
but this can be hardly considered to be "bringing up something for a 
discussion" when someone doesn't even make a point (like e.g. "I think it 
should be changed because..."). Ad absurdum I could say: Because of 
because-it-can-hurt-someones-feelings reasons it would be nice to...

> I don't recall that there were arguments a few months ago on the PR to make 
> the docs gender neutral.  Maybe people were against that too as being 'too 
> politically correct', but they didn't feel the need to talk about.  To me, 
> this issue is similar to that one.

_Personally_, I consider that to be the same kind of PC/SJW nonsense and there 
should've been a similar discussion. However, there's a big difference. Making 
documentation gender neutral is unnecessary but it doesn't affect any 
established CS terminology and doesn't introduce artificial terminological 
inconsistency between related technologies. 

> But, I think it's mostly because it's what we're used to.

Yes, and that's what is established terminology about.

> Here's an idea -- find a friend and explain to them that there is a concept 
> in computer science...

When you enter a new field a part of your responsibility is to learn its 
terminology and not voluntarily change it because it somehow affects you (hurts 
your feelings, not compatible with your political view point etc.). Imagine 
doing the same thing in physics, chemistry or mathematics. Would you redefine 
number 1 for diversity reasons (there are ways for making up diversity reasons 
even for this*)? The terminology used inside a field is primarily for the 
people who are inside the field and understand it.

My arguments can sound a bit sarcastic as they try to illustrate the absurdity 
of this whole issue. They are by no means personal. Seeing all the PC/SJW 
nonsense around me, I'm afraid that this can be the starting of Python becoming 
PCython (by which I don't mean a combination of Python with Cython :)).

* To see how far could this go, look at this video: 
https://www.youtube.com/watch?v=iKcWu0tsiZM

--
nosy: +skrah

___
Python tracker 

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

[issue34580] sqlite doc: clarify the scope of the context manager

[Daniel Jakots]

Daniel Jakots  added the comment:

Thanks for working on this bug!

My message focussed on the closing aspect because that was my problem. :)

Maybe the wording should be more general like:
- "Note that this does not automatically call :meth:`close` on the connection 
object."
+ "Note that this does not automatically handle the connection object."

(I'm not sure if I should comment here or on the PR on gh)

--

___
Python tracker 

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