search

indygreg / python-build-standalone

Produce redistributable builds of Python
BSD 3-Clause "New" or "Revised" License
1.71k stars 107 forks source link

Suggestion: "Nightly" Builds #139

Open ryancinsight opened 1 year ago

ryancinsight commented 1 year ago

Using "nightly" loosely but having an option to use the greatest in newest release candidate could help debug early on/find bugs that didn't previously cause issues due to new usage/allow users to test new improvements and if need be delay distribution with the new more significant changes in speed from previous versions.

indygreg commented 1 year ago

I'm supportive of this.

But the main reason we don't have this is supporting the latest CPython branch tends to require a lot of code changes over the evolution of a major CPython release. I've found it easier to just set aside 1-2 days every year to apply all changes in bulk than to attempt to track upstream more closely.

There's a compelling argument that it would be easier to adopt to upstream changes if we were building off the latest CPython branches. But if we do this, I can't make any guarantees that builds remain green. python-build-standalone is very much something I prefer to touch once every few months and I'd prefer to not get sidetracked by random CPython commits breaking our build.

zanieb commented 3 months ago

I'll look into this