[issue23084] Expose C struct timespec (nanosecond resolution) in time module

mdcb added the comment: naively and coming from C, you have time_t to represent time so even though underneath it's typedef, it gives the casual user like me comfort (2038 not accounted). I don't know the details why struct timespec was chosen rather than nanoseconds as integer, and in fact wo

[issue18590] Found text not always highlighted by Replace dialog on Windows

Terry J. Reedy added the comment: Additional notes: Sarah's Replace patch consists of the tag raise. I just verified the reason why it works and moved it to the dialog base to include output windows and soon, Search dialogs. Sarah, if you do not provide a 'family' name, I will list you in Mi

[issue9694] argparse required arguments displayed under "optional arguments"

Martin Panter added the comment: Updated my patch with a “version changed” notice -- Added file: http://bugs.python.org/file37505/option-internal.patch ___ Python tracker ___

[issue22341] Python 3 crc32 documentation clarifications

Martin Panter added the comment: Here is a patch that fixes the binascii, zlib.crc32() and adler32() documentation as I suggested. I’m still interested why there are two ways to do a CRC-32, each equally non-obvious as the other. -- keywords: +patch Added file: http://bugs.python.org/

[issue18590] Found text not always highlighted by Replace dialog

Terry J. Reedy added the comment: I am narrowing the scope of this issue to Replace dialogs and widening the scope to output as well as edit windows. The attached patch solves the issue as redefined. (It has a temporary hack to pass the unittests.) For edit windows, the problem is that the de

[issue23088] Document that PyUnicode_AsUTF8() returns a null-terminated string

New submission from Martin Panter: As discussed in msg232863, and later confirmed in the code -- assignee: docs@python components: Documentation files: utf8-null.patch keywords: patch messages: 232925 nosy: docs@python, vadmium priority: normal severity: normal status: open title: Docume

[issue22350] nntplib file write failure causes exception from QUIT command

Martin Panter added the comment: Here is a patch with a fix and a test -- keywords: +patch Added file: http://bugs.python.org/file37501/fail-close.patch ___ Python tracker ___ __

[issue23080] BoundArguments.arguments should be unordered

Yury Selivanov added the comment: I'd like to see PEP 468 explicitly rejected or postponed till 3.6 before we make this change in 3.5. -- ___ Python tracker ___

[issue23081] Document PySequence_List(o) as equivalent to list(o)

Changes by Berker Peksag : -- nosy: +berker.peksag, tim.peters ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23080] BoundArguments.arguments should be unordered

Changes by Berker Peksag : -- nosy: +yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Alexander Belopolsky added the comment: "nanosecond support [in Python]" is a PEP-size topic. As Victor suggested, "If you are motivated enough, you may update the PEP and write a new one." The tracker does not provide a sufficiently large forum to discuss "nanosecond support" in full genera

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

mdcb added the comment: firefox did something and changed some fields I did not intend to. I'm trying to undo that now. -- resolution: -> rejected status: open -> pending ___ Python tracker __

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

mdcb added the comment: I'm fine my patch doesn't resolve the "nanosecond support", but that doesn't mean the issue is closed per say. Ref. to PEP410 rejection and de facto standard seems a bit expeditive. assuming it worked, this would somewhat be more agreeable ? >class timestamp(int): pass

[issue23082] pathlib relative_to() can give confusing error message

Changes by Arfrever Frehtes Taifersar Arahesis : -- assignee: -> pitrou nosy: +Arfrever, pitrou ___ Python tracker ___ ___ Python-bug

[issue23076] list(pathlib.Path().glob("")) fails with IndexError

Arfrever Frehtes Taifersar Arahesis added the comment: >>> list(pathlib.Path().glob("")) Traceback (most recent call last): File "", line 1, in File "/usr/lib64/python3.5/pathlib.py", line 999, in glob selector = _make_selector(tuple(pattern_parts)) File "/usr/lib64/python3.5/functools

[issue8934] aifc should use str instead of bytes (wave, sunau compatibility)

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue21071] struct.Struct.format is bytes, but should be str

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue16349] Document whether it's safe to use bytes for struct format string

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Alexander Belopolsky added the comment: > can we change back the title because in fact Please don't. If you would like to discuss general ideas - the right forum would be the "python-ideas" mailing list. We have no shortage of issue numbers: once you have another specific proposal - feel fre

[issue19104] pprint produces invalid output for long strings

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue22179] Idle. Search dialog found text not highlited on Windows

Terry J. Reedy added the comment: The first # comment above should be "On Windows, the selection highlight is *not* visible while the modal dialog is open." This bug was, in a sense, introduced by #17511, which kept the dialog open after [Find] is pressed, instead of closing it immediately.

[issue18590] 'Search' and 'Replace' dialogs don't work on quoted text in Windows

Changes by Terry J. Reedy : -- dependencies: -Idle. Search dialog found text not highlited on Windows ___ Python tracker ___ ___ Pyth

[issue22995] Restrict default pickleability

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue22113] memoryview and struct.pack_into

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Alexander Belopolsky added the comment: > but that seems to loose the type information after doing arithmetics Hear, hear. See #2267. If you find out why Python was designed this way - let me know. -- ___ Python tracker

[issue23087] Exec variable not found error

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

mdcb added the comment: can we change back the title because in fact, exposing struct timespec wasn't really the intention (but keep the patch if you want it!) -- ___ Python tracker ___

[issue23085] update internal libffi copy to 3.2.1

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23042] Python 2.7.9 ctypes module doesn't build on FreeBSD x86

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Alexander Belopolsky added the comment: > If I am reading data from an external device that has nanosecond > resolution, how would I create such a time stamp in Python right now? seconds * 10**9 + nanoseconds (translated to C API if necessary) -- __

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

mdcb added the comment: I'm going to be my own devil's advocate: PyLong_FromLong ... Thanks for all the links, I hadn't realized there was so much background to the issue, there is some good reading there too. you've changed the title now, but in fact the intention was the other aspect, core

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Ethan Furman added the comment: If I am reading data from an external device that has nanosecond resolution, how would I create such a time stamp in Python right now? -- ___ Python tracker

[issue23001] Accept mutable bytes-like objects

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Alexander Belopolsky added the comment: I would say that rejection note for PEP 410 [1] and the implementation of st_[amc]time_ns fields in os.stats() have established a de-facto standard for representing nanosecond resolution timestamps in Python. I think this proposal should be rejected. [1

[issue23084] Expose C struct timespec (nanosecond resolution) in time module

Changes by Alexander Belopolsky : -- title: nanosecond support -> Expose C struct timespec (nanosecond resolution) in time module ___ Python tracker ___

[issue23087] Exec variable not found error

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue23084] nanosecond support

Ethan Furman added the comment: Just keep the word nanasecond in there somewhere, as that is the motivating purpose behind the patch. -- ___ Python tracker ___ _

[issue18590] 'Search' and 'Replace' dialogs don't work on quoted text in Windows

Terry J. Reedy added the comment: I should note that in msg225543 of #22179, I verified that there is a problem in Replace for highlighting found text within quotes, as well as in keywords, until the dialog is closed. On the other hand, the same text is hihglighted in identifiers, plain code,

[issue23084] nanosecond support

Alexander Belopolsky added the comment: Would anyone object if I rename this issue to "Expose C struct timespec in time module"? The current title is way too broad. -- ___ Python tracker _

[issue23087] Exec variable not found error

New submission from Keith Chewning: If I %paste this code into an ipython shell the test passes. If this is saved to a file DictTest.py and run with ./DictTest.py -m the test fails. with the error name 'keys' is not defined If the variable keys is made global, as is suggested in the comment,

[issue23084] nanosecond support

STINNER Victor added the comment: > C implementation of datetime.now() does not rely on float time, so this is > only an issue for the Python implementation. Ah yes, but there is another technical issue that I'm trying to address in the issue #22117: datetime.datetime.now() is implemented with

[issue23084] nanosecond support

Alexander Belopolsky added the comment: > it would be possible for datetime.datetime.now() > to avoid the float time. C implementation of datetime.now() does not rely on float time, so this is only an issue for the Python implementation. Moreover, as long as datetime keeps its microsecond reso

[issue23086] Add start and stop parameters to the Sequence.index() ABC mixin method

New submission from Raymond Hettinger: Currently, the Sequence ABC doesn't support start and stop arguments for the index() method which limits its usefulness in doing repeated searches (iterating over a target value) and which limits it substitutablity for various concrete sequences such as t

[issue23085] update internal libffi copy to 3.2.1

Marc-Andre Lemburg added the comment: Will this also fix http://bugs.python.org/issue23042 ? -- nosy: +lemburg ___ Python tracker ___

[issue22956] Improved support for prepared SQL statements

Changes by mike bayer : -- nosy: +zzzeek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue23084] nanosecond support

STINNER Victor added the comment: See the issue #22117 which basically implement the PEP 410, but only for private C API. The idea is to avoid loss of precision caused by the float type when it is possible. For example, it would be possible for datetime.datetime.now() to avoid the float time.

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Removed file: http://bugs.python.org/file37499/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Added file: http://bugs.python.org/file37500/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Added file: http://bugs.python.org/file37499/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Removed file: http://bugs.python.org/file37498/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Added file: http://bugs.python.org/file37498/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Removed file: http://bugs.python.org/file37497/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue22038] Implement atomic operations on non-x86 platforms

Gustavo Temple added the comment: @haypo, done: atomicv3.patch -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue22038] Implement atomic operations on non-x86 platforms

Changes by Gustavo Temple : Added file: http://bugs.python.org/file37497/atomicv3.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue23085] update internal libffi copy to 3.2.1

Steve Dower added the comment: As I mentioned on the other post, libffi's current version bears no relation to what we have in CPython, so the patches don't apply. I'm not planning on rewriting CPython patches so that they will apply to libffi, nor do I intend to replace our current version of

[issue23085] update internal libffi copy to 3.2.1

Matthias Klose added the comment: you should actively drive upstream integration, and ping patches if they are not addressed. -- ___ Python tracker ___ _

[issue21236] patch to use cabinet.lib instead of fci.lib (fixes build with Windows SDK 8.0)

Steve Dower added the comment: This was fixed with #22919. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue23085] update internal libffi copy to 3.2.1

Steve Dower added the comment: I think Matthias is referring to #20160, but as far as I could tell libffi is multiple versions ahead of the version in Python and already has the fixes. I was told to wait for it to be submitted/accepted upstream, so I've been waiting :) -- ___

[issue23084] nanosecond support

Alexander Belopolsky added the comment: > time() could be used to produce them How? -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue23084] nanosecond support

Alexander Belopolsky added the comment: > .. the intent is not for better sleep support, but simply > to be able to create and record time data which contains nano-seconds. Can you describe a specific use-case? What's the advantage of the proposed time.struct_timespec over say >>> timespec =

[issue23084] nanosecond support

Ethan Furman added the comment: I haven't reviewed the patch yet, but I believe the intent is not for better sleep support, but simply to be able to create and record time data which contains nano-seconds. python-dev discussion here: https://mail.python.org/pipermail/python-dev/2014-Decembe

[issue23085] update internal libffi copy to 3.2.1

Gustavo Temple added the comment: @doko, sorry, but what are the Steve's changes? The issue #22733? -- ___ Python tracker ___ ___ Pyth

[issue23084] nanosecond support

Alexander Belopolsky added the comment: See also discussion in #9079, #14127 and #14180. At some point there was some resistance to use capsule mechanism to share code within stdlib and the functions that were shared between time and datetime modules were moved to the core. I am -1 on adding

[issue23083] sys.exit with bool parameter

Changes by Eric V. Smith : -- stage: -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue23085] update internal libffi copy to 3.2.1

Changes by Gustavo Temple : -- title: update internal libffi copy to 3.1 -> update internal libffi copy to 3.2.1 ___ Python tracker ___ _

[issue23085] update internal libffi copy to 3.1

Matthias Klose added the comment: some issues: - the local change for Windows still needs upstream forwarding. Steve, any progress on this? - the libffi.diff is not updated (including Steve's changes) - this should be applied to 2.7 as well. -- nosy: +steve.dower, tim.golden, za

[issue23085] update internal libffi copy to 3.1

New submission from Gustavo Temple: Link to the file: https://github.com/gustavotemple/cpython/pull/2.diff Link to the changes: https://github.com/gustavotemple/cpython/pull/2/commits -- components: ctypes files: libffi.patch keywords: patch messages: 232890 nosy: doko, gustavotemple, m

[issue23084] nanosecond support

Changes by Ethan Furman : -- nosy: +belopolsky, ethan.furman, lemburg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue23084] nanosecond support

Changes by mdcb : -- hgrepos: -289 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mai

[issue23084] nanosecond support

New submission from mdcb: nanosecond support has been discussed at length on python-dev and issue 15443. POSIX.1b defines a struct timespec that is commonly used in C, and seems a good candidate to add core nanosecond support. kernel's time-related structs typically end up in the time module.

[issue22113] memoryview and struct.pack_into

Changes by Serhiy Storchaka : -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue23083] sys.exit with bool parameter

Raymond Hettinger added the comment: I agree that the docs are best as-is. -- nosy: +rhettinger resolution: -> rejected status: open -> closed ___ Python tracker ___ ___

[issue22995] Restrict default pickleability

Changes by Serhiy Storchaka : -- keywords: +patch Added file: http://bugs.python.org/file37494/pickle_restrictions.diff ___ Python tracker ___ ___

[issue22995] Restrict default pickleability

Serhiy Storchaka added the comment: Here is sample patch which adds two restrictions. Default reduce method for protocol >= 2 will forbid pickling objects: 1) When tp_new == NULL. 2) Builtins without any of pickle-related methods: __getnewargs_ex__, __getnewargs__ or __getstate__. Are there

[issue6792] Distutils-based installer does not detect 64bit versions of Python

Changes by Piotr Dobrogost : -- nosy: +piotr.dobrogost ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue23001] Accept mutable bytes-like objects

Changes by Serhiy Storchaka : -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue22896] Don't use PyObject_As*Buffer() functions

Changes by Serhiy Storchaka : -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue19104] pprint produces invalid output for long strings

Changes by Serhiy Storchaka : -- keywords: +needs review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue23083] sys.exit with bool parameter

R. David Murray added the comment: Hmm. Good point about the anti-pattern. I agree that it is probably best to leave the docs as they are. -- ___ Python tracker ___ __

[issue23083] sys.exit with bool parameter

Eric V. Smith added the comment: I'm not sure this should be documented. It follows from int and bool equivalence. Plus, I consider it an anti-pattern. We don't want to document everywhere you can pass a bool where an int is called for. That's thousands of places. -- nosy: +eric.smith

[issue23083] sys.exit with bool parameter

R. David Murray added the comment: >>> issubclass(bool, int) True >>> True == 1 True [41846 refs] >>> False == 0 True This is fundamental to Python, so it is not obvious that it is a good idea to mention bool explicitly in the sys.exit docs. Perhaps we could change it to say "int (or an int s

[issue23083] sys.exit with bool parameter

New submission from Polux Moon: when using a bool as parameter implementation (2.7) behave like: sys.exit(True) <=> sys.exit(1) sys.exit(False) <=> sys.exit(0) so the bool indicate if the termination is abnormal following the doc it should be equivalent to sys.exit(1) in all cases if we assume

[issue19918] PureWindowsPath.relative_to() is not case insensitive

Antoine Pitrou added the comment: pathlib is case-sensitive under OS X (under any non-Windows platform actually). -- ___ Python tracker ___ __

[issue23079] os.path.normcase documentation confusing

Serhiy Storchaka added the comment: > Or would s/case-insensitive/not case-preserving/ be more accurate? (Well, > you'd probably rewrite the sentence to eliminate the 'not'). This would not be more accurate because behavior depends from OS, not from file system. On Unix/Linux your can mount ca

[issue21071] struct.Struct.format is bytes, but should be str

R. David Murray added the comment: A backward compatibility break would certainly need to be discussed, IMO. -- ___ Python tracker ___ ___

[issue23079] os.path.normcase documentation confusing

R. David Murray added the comment: Or would s/case-insensitive/not case-preserving/ be more accurate? (Well, you'd probably rewrite the sentence to eliminate the 'not'). -- nosy: +r.david.murray ___ Python tracker

[issue19918] PureWindowsPath.relative_to() is not case insensitive

Chris Jerdonek added the comment: Was this also fixed for Mac OS X? Mac OS X is also case-insensitive by default, and on Python 3.4.2 I'm getting: >>> Path("Foo").relative_to("foo") Traceback (most recent call last): File "", line 1, in File "/opt/local/Library/Frameworks/Python.framewor

[issue23082] pathlib relative_to() can give confusing error message

Chris Jerdonek added the comment: By the way, here is another (less) confusing error message: >>> Path("foo").relative_to("fo") Traceback (most recent call last): File "", line 1, in File "/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/pathlib.py"

[issue23082] pathlib relative_to() can give confusing error message

New submission from Chris Jerdonek: pathlib's relative_to(other) can give a confusing message when "other" is os.curdir. For example-- Python 3.4.2 (default, Nov 12 2014, 18:23:59) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.54)] on darwin Type "help", "copyright", "credits"

[issue23081] Document PySequence_List(o) as equivalent to list(o)

New submission from Lars Buitinck: PySequence_List has accepted iterables since changeset 6c82277e77f3 of May 1, 2001 ("NEEDS DOC CHANGES" :), but its documentation still only speaks of sequences. I suggest that it is changed to promise to handle arbitrary iterables, just like PySequence_Tuple

[issue23080] BoundArguments.arguments should be unordered

New submission from Antony Lee: This patch makes BoundArguments.arguments an unordered dict. As discussed on python-ideas, the rationale for this is 1. The current ordering in ba.arguments is the one of the parameters in the signature (which is already available via the ba.signature attribute

[issue23079] os.path.normcase documentation confusing

Serhiy Storchaka added the comment: ... and OS/2 (in 2.7). -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue23079] os.path.normcase documentation confusing

Serhiy Storchaka added the comment: s/on case-insensitive filesystems/on Windows/ ? -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue23079] os.path.normcase documentation confusing

New submission from Chris Jerdonek: The documentation for os.path.normcase(path) is currently confusing or self-contradictory. Currently, it reads-- "Normalize the case of a pathname. On Unix and Mac OS X, this returns the path unchanged; on case-insensitive filesystems, it converts the path

[issue21697] shutil.copytree() handles symbolic directory incorrectly

Björn Dahlgren added the comment: I ran across this bug too. Applying Eduardo's patch got my package working under Py 3.4 -- nosy: +Björn.Dahlgren ___ Python tracker ___

[issue23071] codecs.__all__ incomplete

Marc-Andre Lemburg added the comment: +1 -- nosy: +lemburg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue21071] struct.Struct.format is bytes, but should be str

Serhiy Storchaka added the comment: I think breaking the compatibility should be discussed on Python-Dev. Similar issue (and even worse) is issue8934. -- nosy: +serhiy.storchaka ___ Python tracker

[issue23071] codecs.__all__ incomplete

Serhiy Storchaka added the comment: LGTM. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

  1   2   >