Skip to content

PEP 774: Add Discussions-To link and minor revisions #4236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
savannahostrowski merged 5 commits into from
Jan 28, 2025
Merged

PEP 774: Add Discussions-To link and minor revisions #4236

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a1a7f36
PEP 744: Add Discussions-To link
savannahostrowski Jan 27, 2025
472d9e2
PEP 744: Remove extraneous .
savannahostrowski Jan 27, 2025
9898642
PEP 774: Remove stale section
savannahostrowski Jan 28, 2025
23abbe4
Update pep-0774.rst
savannahostrowski Jan 28, 2025
78d031e
PEP 744: Remove , from URL
savannahostrowski Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions peps/pep-0774.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
PEP: 774
Title: Removing the LLVM requirement for JIT builds
Author: Savannah Ostrowski <savannah@python.org>
Discussions-To: https://discuss.python.org/t/78548/
Status: Draft
Type: Standards Track
Created: 27-Jan-2025
Expand Down Expand Up @@ -220,9 +221,7 @@ process. Additional tooling would be required to fetch the stencils and
potentially create additional and unnecessary failure points in the workflow.
This separation also makes it harder to ensure consistency between the stencils
and the CPython source tree, as updates must be coordinated across the
repositories. Finally, this approach introduces an attack vector, as external
repositories are less integrated with our workflows, making provenance and
integrity harder to guarantee.
repositories.

Hosting in cloud storage
------------------------
Expand All @@ -241,7 +240,7 @@ use Git LFS. Git LFS does not work well with offline workflows since files
managed by LFS require an internet connection to fetch when checking out
specific commits, which is disruptive for even basic Git workflows. Git LFS has
some free quota but there are `additional
costs <https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage>`__.
costs <https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage>`__
for exceeding that quota which are also undesirable.

Maintain the status quo with LLVM as a build-time dependency
Expand Down
Loading