Search results

...ange is about what happens once [https://www.python.org/dev/peps/pep-0394/ PEP 394] is updated (and we will drive that update if needed): ...]], where the main argument was [https://www.python.org/dev/peps/pep-0394/ PEP 394] that says: ''for the time being, all distributions should ensure that

[https://peps.python.org/pep-0668/ PEP 668 – Marking Python base environments as “externally managed”] prop See [https://peps.python.org/pep-0668/ PEP 668 – Marking Python base environments as “externally managed”].

...d according to [https://www.python.org/dev/peps/pep-0503/#normalized-names PEP 503]. E.g. on Fedora 36 a package provides both `python3dist(ruamel-yaml)` ...e packages via a name with a dash. Hence, we have slowly been migrating to PEP 503 name normalization.

...eam has now released 3.2 (see the upstream [http://www.python.org/dev/peps/pep-0392/ release schedule]) ...se of the Python 3 language. Although the [http://www.python.org/dev/peps/pep-3003/ core language has been frozen] (to allow the [[SIGs/Python#Python_Run

Reflecting the recent changes of [https://www.python.org/dev/peps/pep-0394/ PEP 394] -- ''The "python" Command on Unix-Like Systems'', we are moving <code> The upstream recommendation ([https://www.python.org/dev/peps/pep-0394/ PEP 394]), which we try to follow in Fedora, is that users -- not distros, and

...in PEP (Python Enhancement Proposal) 538: https://www.python.org/dev/peps/pep-0538/ The PEP has no strong opposition upstream, but acceptance is held back by considera

...optimizations. See the upstream notes at [https://www.python.org/dev/peps/pep-0537/#features-for-3-7 Features for 3.7] and [https://docs.python.org/3.7/w (From [https://www.python.org/dev/peps/pep-0537/#schedule Python 3.7 Release Schedule] and [[Releases/29/Schedule|Fedo

* Python (making use of devpi and the explicit redistributor support in PEP 440)

Patch related to [https://www.python.org/dev/peps/pep-0552/ PEP 552: Deterministic pycs] implemented in Python 3.7.

...ges to the upstream guidance in [https://www.python.org/dev/peps/pep-0394/ PEP 394]

...changes (even if we e.g. ported [http://www.python.org/dev/peps/pep-3147/ PEP 3147], we still ought to rebuild the RPMs)

...he invalidation is described in [https://www.python.org/dev/peps/pep-0552/ PEP 552]. ...erent filenames as described in [https://www.python.org/dev/peps/pep-0488/ PEP 488].

...nt] upstream recommendations in [https://www.python.org/dev/peps/pep-0394/ PEP 394]. ...s/pull/989 upstream changes] to [https://www.python.org/dev/peps/pep-0394/ PEP 394] recommendations.

| 397 || CVE-2007-4559, PEP 706: Filter for tarfile.extractall || RHEL (TBD) || Not yet |[https://www.python.org/dev/peps/pep-0538/ PEP 538]

* deep integration with PEP 484 typing practices and current capabilities, particularly within the ORM,

...ream [https://www.python.org/dev/peps/pep-0432/#a-system-python-executable PEP 432].

...e upstream's decisions, especially that [https://peps.python.org/pep-0440/ PEP 440] doesn't forbid using the version `0.0.0`. OTOH [https://semver.org/ se

...renamed from System Python to Platform Python not to collide with upstream PEP 432.

...encouraged to use versions adherent to [https://peps.python.org/pep-0440/ PEP 440].

Since Python 3.9 and [https://www.python.org/dev/peps/pep-0615/ PEP 615], the package is no longer necessary. The [https://docs.python.org/3.9/