| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Currently modules which are imported early are misreported in coverage. A fix is documented in the devguide, but the fix wasn't being used in CI.
|
| |
|
| |
|
|
|
| |
Automerge-Triggered-By: @Mariatta
|
| |
|
|
|
| |
Signed-off-by: Filipe Laíns <lains@archlinux.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the initial implementation of PEP 615, the zoneinfo module,
ported from the standalone reference implementation (see
https://www.python.org/dev/peps/pep-0615/#reference-implementation for a
link, which has a more detailed commit history).
This includes (hopefully) all functional elements described in the PEP,
but documentation is found in a separate PR. This includes:
1. A pure python implementation of the ZoneInfo class
2. A C accelerated implementation of the ZoneInfo class
3. Tests with 100% branch coverage for the Python code (though C code
coverage is less than 100%).
4. A compile-time configuration option on Linux (though not on Windows)
Differences from the reference implementation:
- The module is arranged slightly differently: the accelerated module is
`_zoneinfo` rather than `zoneinfo._czoneinfo`, which also necessitates
some changes in the test support function. (Suggested by Victor
Stinner and Steve Dower.)
- The tests are arranged slightly differently and do not include the
property tests. The tests live at test/test_zoneinfo/test_zoneinfo.py
rather than test/test_zoneinfo.py or test/test_zoneinfo/__init__.py
because we may do some refactoring in the future that would likely
require this separation anyway; we may:
- include the property tests
- automatically run all the tests against both pure Python and C,
rather than manually constructing C and Python test classes (similar
to the way this works with test_datetime.py, which generates C
and Python test cases from datetimetester.py).
- This includes a compile-time configuration option on Linux (though not
on Windows); added with much help from Thomas Wouters.
- Integration into the CPython build system is obviously different from
building a standalone zoneinfo module wheel.
- This includes configuration to install the tzdata package as part of
CI, though only on the coverage jobs. Introducing a PyPI dependency as
part of the CI build was controversial, and this is seen as less of a
major change, since the coverage jobs already depend on pip and PyPI.
Additional changes that were introduced as part of this PR, most / all of
which were backported to the reference implementation:
- Fixed reference and memory leaks
With much debugging help from Pablo Galindo
- Added smoke tests ensuring that the C and Python modules are built
The import machinery can be somewhat fragile, and the "seamlessly falls
back to pure Python" nature of this module makes it so that a problem
building the C extension or a failure to import the pure Python version
might easily go unnoticed.
- Adjustments to zoneinfo.__dir__
Suggested by Petr Viktorin.
- Slight refactorings as suggested by Steve Dower.
- Removed unnecessary if check on std_abbr
Discovered this because of a missing line in branch coverage.
|
|
|
|
|
| |
(GH-20097)
Signed-off-by: Filipe Laíns <lains@archlinux.org>
|
|
|
| |
Signed-off-by: Filipe Laíns <lains@archlinux.org>
|
|
|
|
|
| |
Always run GitHub action jobs, even on documentation-only pull
requests. So it will be possible to make a GitHub action job, like
the Windows (64-bit) job, mandatory.
|
| |
|
| |
|
|
|
|
| |
Co-authored-by: Guido van Rossum <guido@python.org>
Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
|
|
|
| |
Update also OpenSSL version in Ubuntu and Coverage jobs.
|
|
|
|
|
| |
(GH-18918)
Also adds GitHub CI test for Windows installer changes
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
https://bugs.python.org/issue39041
Automerge-Triggered-By: @zooba
|
|
|
| |
Also skip build for doc-only changes and enable on push
|
| |
|
| |
|
| |
|
|
|
| |
Add Ethan Furman for enum, cgi, and cgitb.
|
| |
|
|
|
|
|
| |
Add myself to the codeowners file as I would like to
be automatically added as a reviewer for PRs that touch
that component and its documentation.
|
| |
|
| |
|
| |
|
|
|
| |
Also adds abalkin to CODEOWNERS for date and time related files.
|
| |
|
| |
|
|
|
| |
This reverts commit 71dc7c5fbd856df83202f39c1f41ccd07c6eceb7. Turns out you must have write access for CODEOWNERS to work.
|
| |
|
| |
|
|
|
| |
There is a duplicated "in" in the Supported Versions text.
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 📝 Add a GitHub-specific security page
It will show up @
https://github.com/python/cpython/security/policy
allowing to navigate users who get there from "Security" tab in the
GitHub repo to the full article explaining the security vulnerability
reporting practices.
Co-Authored-By: Hugo <hugovk@users.noreply.github.com>
|
| |
|
|
|
|
|
| |
Add myself to the codeowners file as I would like to
be automatically added as a reviewer for PRs that touch
that component.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Previously, Python was built in 32-bit mode and so issues specific to
64-bit mode like compiler warnings could be missed.
|
|
|
|
|
| |
Follow up from https://github.com/python/peps/pull/712#issuecomment-403591108:
"people using the repo without using GitHub still ought to be reminded of the COC" - GvR
|
| |
|
|
|
|
|
|
| |
* Prevent spurious message if taking a shortcut
* Fix YAML style
* Disable largefile tests
|