summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Turn off AppVeyor CI (GH-15929)Zachary Ware2019-09-111-38/+0
|
* bpo-33459: Fix "tuple displays" term in Expressions.rst (GH-6760)Andre Delfino2019-09-111-4/+4
| | | | | | | https://bugs.python.org/issue33459 Automerge-Triggered-By: @matrixise
* bpo-34519: Add additional aliases for HP Roman 8 (GH-8956)Michael Osipov2019-09-112-0/+3
| | | | | | | * bpo-34519: Add additional aliases for HP Roman 8 HP Roman 8 is known under mode aliases than listed in aliases.py. Patch by Michael Osipov.
* bpo-38107: Replace direct future and task contructor calls with factories in ↵Andrew Svetlov2019-09-1113-159/+156
| | | | asyncio tests (GH-15928)
* bpo-35640: Allow passing PathLike arguments to SimpleHTTPRequestHandler ↵Géry Ogam2019-09-114-24/+80
| | | | (GH-11398)
* Doc: Use walrus operator in example. (GH-15934)Julien Palard2019-09-111-4/+1
|
* bpo-35943: Prevent PyImport_GetModule() from returning a ↵Joannah Nanjekye2019-09-112-23/+48
| | | | partially-initialized module (GH-15057)
* Doc: Fix typo in fastsearch comments (GH-14608)Valentin Haenel2019-09-111-2/+2
|
* bpo-37326: Include libffi license when available (GH-15921)Steve Dower2019-09-111-2/+3
|
* bpo-35649: update http client example (GH-11441)Ashwin Ramaswami2019-09-111-2/+5
|
* Minor ReST formatting fixes in subprocess docs (#14876)Tim Hoffmann2019-09-111-4/+4
|
* bpo-35603: Add a note on difflib table header interpreted as HTML (GH-11439)Xtreak2019-09-111-0/+4
|
* bpo-20504 : in cgi.py, fix bug when a multipart/form-data request has… ↵Pierre Quentel2019-09-113-3/+24
| | | | | | | | | | | | (#10638) * bpo-20504 : in cgi.py, fix bug when a multipart/form-data request has no content-length header * Add Misc/NEWS.d/next file. * Add rst formatting for NEWS.d/next file * Reaplce assert by self.assertEqual
* bpo-35168: Make shlex.punctuation_chars read-only (#11631)Alex2019-09-114-4/+18
| | | | | | | | * bpo-35168: Documentation about shlex.punctuation_chars now states that it should be set in __init__.py * bpo-35168: Convert shlex.punctuation_chars to read-only property * Add NEWS.d entry
* bpo-32972: Document IsolatedAsyncioTestCase of unittest module (GH-15878)Xtreak2019-09-113-1/+103
| | | | | | | | | | | * Document `unittest.IsolatedAsyncioTestCase` API * Add a simple example with respect to order of evaluation of setup and teardown calls. https://bugs.python.org/issue32972 Automerge-Triggered-By: @asvetlov
* bpo-37151: remove special case for PyCFunction from PyObject_Call (GH-14684)Jeroen Demeyer2019-09-116-66/+47
| | | | | | | bpo-37151: remove special case for PyCFunction from PyObject_Call Alse, make the undocumented function PyCFunction_Call an alias of PyObject_Call and deprecate it.
* bpo-38103: fix conflicting labels in the docs. (GH-15906)Ezio Melotti2019-09-112-5/+5
|
* bpo-35066: Make trailing percent test more portable. (GH-15907)Benjamin Peterson2019-09-111-4/+9
| | | Different libc implementations have different behavior when presented with trailing % in strftime strings. To make test_strftime_trailing_percent more portable, compare the output of datetime.strftime directly to that of time.strftime rather than hardcoding.
* bpo-28494: install ziptestdata to fix install bot (GH-15902)Gregory P. Smith2019-09-111-0/+1
|
* bpo-25810: Clarify eval() docs, it does not keywords (GH-15173)smokephil2019-09-111-1/+1
|
* bpo-37409: fix relative import with no parent (#14956)Ben Lewis2019-09-115-11/+25
| | | | | | | | | | | | | Relative imports use resolve_name to get the absolute target name, which first seeks the current module's absolute package name from the globals: If __package__ (and __spec__.parent) are missing then import uses __name__, truncating the last segment if the module is a submodule rather than a package __init__.py (which it guesses from whether __path__ is defined). The __name__ attempt should fail if there is no parent package (top level modules), if __name__ is '__main__' (-m entry points), or both (scripts). That is, if both __name__ has no subcomponents and the module does not seem to be a package __init__ module then import should fail.
* bpo-37585: Add clarification regarding comparing dict.values() (GH-14954)Kyle Stanley2019-09-111-0/+8
|
* bpo-16438: Doc: confusing text regarding numeric precedence corrected (GH-10521)Anjali2019-09-111-3/+2
|
* bpo-38081: Fixes ntpath.realpath('NUL') (GH-15899)Steve Dower2019-09-113-6/+12
|
* bpo-37936: Systematically distinguish rooted vs. unrooted in .gitignore ↵Greg Price2019-09-113-51/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (GH-15823) A root cause of bpo-37936 is that it's easy to write a .gitignore rule that's intended to apply to a specific file (e.g., the `pyconfig.h` generated by `./configure`) but actually applies to all similarly-named files in the tree (e.g., `PC/pyconfig.h`.) Specifically, any rule with no non-trailing slashes is applied in an "unrooted" way, to files anywhere in the tree. This means that if we write the rules in the most obvious-looking way, then * for specific files we want to ignore that happen to be in subdirectories (like `Modules/config.c`), the rule will work as intended, staying "rooted" to the top of the tree; but * when a specific file we want to ignore happens to be at the root of the repo (like `platform`), then the obvious rule (`platform`) will apply much more broadly than intended: if someone tries to add a file or directory named `platform` somewhere else in the tree, it will unexpectedly get ignored. That's surprising behavior that can make the .gitignore file's behavior feel finicky and unpredictable. To avoid it, we can simply always give a rule "rooted" behavior when that's what's intended, by systematically using leading slashes. Further, to help make the pattern obvious when looking at the file and minimize any need for thinking about the syntax when adding new rules: separate the rules into one group for each type, with brief comments identifying them. For most of these rules it's clear whether they're meant to be rooted or unrooted, but in a handful of cases I've only guessed. In that case the safer default (the choice that won't hide information) is the narrower, rooted meaning, with a leading slash. If for some of these the unrooted meaning is desired after all, it'll be easy to move them to the unrooted section at the top.
* bpo-37424: Avoid a hang in subprocess.run timeout output capture (GH-14490)Gregory P. Smith2019-09-113-9/+53
| | | | | | | Fixes a possible hang when using a timeout on subprocess.run() while capturing output. If the child process spawned its own children or otherwise connected its stdout or stderr handles with another process, we could hang after the timeout was reached and our child was killed when attempting to read final output from the pipes.
* Overhaul datetime documentation (GH-13410)Brad2019-09-112-476/+731
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a restructuring of the datetime documentation to hopefully make them more user-friendly and approachable to new users without losing any of the detail. Changes include: - Creating dedicated subsections for some concepts such as: - "Constants" - "Naive vs Aware" - "Determining if an Object is Aware" - Give 'naive vs aware' its own subsection - Give 'constants' their own subsection - Overhauling the strftime-strptime section by: - Breaking it into logical, linkable, and digestable parts - Adding a high-level comparison table - Moving the technical detail to bottom: readers come to this section primarily to remind themselves to things: - How do I write the format code for X? - strptime/strftime: which one is which again? - Touching up fromisoformat + isoformat sections by: - Revising fromisoformat + isoformat for date, time, and datetime - Adding basic examples - Enforcing consistency about putting formats (i.e. ``HH:MM``) in double backticks. This was previously done in some places but not all - Putting long 'supported formats', on their own line to improve readability - Moving the 'seealso' section to the top and add a link to dateutil Rationale: This doesn't really belong nested under the 'constants' section. Let readers know right away that datetime is one of several related tools. - Moving common features of several types into one place: Previously, each type went out of its way to note separately that it was hashable and picklable. These can be brought into one single place that is more prominent. - Reducing some verbose explanations to improve readability - Breaking up long paragraphs into digestable chunks - Displaying longer "equivalent to" examples, as short code blocks - Using the dot notation for datetime/time classes: Use :class:`.time` and :class:`.datetime` rather than :class:`time` and :class:`datetime`; otherwise, the generated links will route to the respective modules, not classes. - Rewording the tzinfo class description The top paragraph should get straight to the point of telling the reader what subclasses of tzinfo _do_. Previously, that was hidden in a later paragraph. - Adding a note on .today() versus .now() - Rearranging and expanding example blocks, including: - Moved long, multiline inline examples to standalone examples - Simplified the example block for timedelta arithmetic: - Broke the example into two logical sections: 1. normalization/parameter 'merging' 2. timedelta arithmetic - Reduced the complexity of the some of the examples. Show reasonable, real-world uses cases that are easy to follow along with and progres in difficult slightly. - Broke up the example sections for date and datetime sections by putting the easy examples first, progressing to more esoteric situations and breaking it up into logical sections based on what the methods are doing at a high level. - Simplified the KabulTz example: - Put the class definition itself into a non-REPL block since there is no interactive output involved there - Briefly explained what's happening before launching into the code - Broke the example section into visually separate chunks - Various whitespace, formatting, style and grammar fixes including: - Consistently using backctics for 'date_string' formats - Consistently using one space after periods. - Consistently using bold for vocab terms - Consistently using italics when referring to params: See https://devguide.python.org/documenting/#id4 - Using '::' to lead into code blocks Per https://devguide.python.org/documenting/#source-code, this will let the reader use the 'expand/collapse' top-right button for REPL blocks to hide or show the prompt. - Using consistent captialization schemes - Removing use of the default role - Put 'example' blocks in Markdown subsections This is a combination of 66 commits. See bpo-36960: https://bugs.python.org/issue36960
* bpo-37879: Suppress subtype_dealloc decref when base type is a C heap type ↵Eddie Elizondo2019-09-114-10/+318
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (GH-15323) The instance destructor for a type is responsible for preparing an instance for deallocation by decrementing the reference counts of its referents. If an instance belongs to a heap type, the type object of an instance has its reference count decremented while for static types, which are permanently allocated, the type object is unaffected by the instance destructor. Previously, the default instance destructor searched the class hierarchy for an inherited instance destructor and, if present, would invoke it. Then, if the instance type is a heap type, it would decrement the reference count of that heap type. However, this could result in the premature destruction of a type because the inherited instance destructor should have already decremented the reference count of the type object. This change avoids the premature destruction of the type object by suppressing the decrement of its reference count when an inherited, non-default instance destructor has been invoked. Finally, an assertion on the Py_SIZE of a type was deleted. Heap types have a non zero size, making this into an incorrect assertion. https://github.com/python/cpython/pull/15323
* bpo-36373: Fix deprecation warnings (GH-15889)Andrew Svetlov2019-09-115-12/+12
| | | https://bugs.python.org/issue36373
* bpo-38034: Fix typo in logging.handlers.rst (GH-15708)wwuck2019-09-111-1/+1
|
* bpo-28494: Test existing zipfile working behavior. (GH-15853)Gregory P. Smith2019-09-106-0/+101
| | | | Add unittests for executables with a zipfile appended to test_zipfile, as zipfile.is_zipfile and zipfile.ZipFile work properly on these today.
* Remove unneeded assignment in PyBytes_Concat() (GH-15274)Sergey Fedoseev2019-09-101-1/+0
| | | The `wb.len = -1` assignment is unneeded since its introduction in 161d695fb0455ce52530d4f43a9eac4c738f64bb as `PyObject_GetBuffer` always fills it in.
* bpo-37574: Mention helper functions for find_spec documentation (GH-14739)jdkandersson2019-09-101-1/+4
|
* bpo-37752: Delete redundant Py_CHARMASK in normalizestring() (GH-15095)Jordon Xu2019-09-107-15/+15
|
* bpo-38089: Move Azure Pipelines to latest VM versions and make macOS tests ↵Steve Dower2019-09-104-4/+7
| | | | optional (GH-15851)
* bpo-32424: Deprecate xml.etree.ElementTree.Element.copy() in favor of ↵Gordon P. Hemsley2019-09-103-0/+39
| | | | copy.copy() (GH-12995)
* bpo-36253: Remove use after free reference in ctypes test suite (GH-12257)Ben Harper2019-09-101-2/+2
|
* bpo-33602: Doc: Remove set and queue references from Data Types (GH-7055)Andre Delfino2019-09-101-3/+4
|
* Docs: Small tweaks to c-api/intro#Include_Files (GH-14698)Kyle Stanley2019-09-101-7/+9
|
* Correct info about "f.read(size)". (GH13852)William Andrea2019-09-101-2/+2
| | | In text mode, the "size" parameter indicates the number of characters, not bytes.
* Correct minor grammatical mistake in open docs (GH-15865)Andre Delfino2019-09-101-2/+2
|
* bpo-37504: Fix documentation build with texinfo builder (GH-14606)Dmitry Shachnev2019-09-102-1/+19
| | | | | | | | | In the table model used by docutils, the `cols` attribute of `tgroup` nodes is mandatory, see [1]. It is used in texinfo builder in [2]. [1]: https://www.oasis-open.org/specs/tm9901.htm#AEN348 [2]: https://github.com/sphinx-doc/sphinx/blob/v2.1.2/sphinx/writers/texinfo.py#L1129 * Doc: Add texinfo support to the Makefile
* bpo-37913: Link to NotImplemented from new docs (GH-15860)Steve Dower2019-09-101-3/+3
|
* bpo-37913: document that __length_hint__ can return NotImplemented (GH-15383)Jeroen Demeyer2019-09-101-2/+4
|
* bpo-38086: Sync importlib.metadata with importlib_metadata 0.21. (GH-15840)Jason R. Coombs2019-09-108-661/+712
| | | https://gitlab.com/python-devs/importlib_metadata/-/tags/0.21
* bpo-38087: Fix case sensitivity in test_pathlib and test_ntpath (GH-15850)Steve Dower2019-09-103-107/+125
|
* bpo-38088: Fixes distutils not finding vcruntime140.dll with only v142 ↵Steve Dower2019-09-102-1/+3
| | | | toolset installed (GH-15849)
* Fix subprocess docstring typo (GH-15812)Matthias2019-09-101-1/+1
|
* Fix typo in ssl.RAND_bytes documentation (GH-14791)Zach Thompson2019-09-101-1/+1
| | | | | It looks like "cryptographically strong" is the preferred phrase from the surrounding documentation. Automerge-Triggered-By: @tiran
* bpo-38090: Fix reference leak in ceval.c (GH-15848)Pablo Galindo2019-09-101-1/+0
|
generated by cgit v0.12 at 2025-08-08 10:01:44 (GMT)