Armin Rigo wrote:
> Do we have any plan to make sys.build_number meaningful in the releases
> as well (generally compiled from an svn export, as Michael pointed out),
> or are we happy with a broken number in this case?
I'm actually a bit confused that Barry changed the meaning of "build
number" for that feature. The build number was meant to count builds,
not revisions (whether this is a useful feature or not).
So I would argue that it is "broken" when it is the result of
svnversion, and "good" when it actually counts builds.
It stopped counting builds on Windows quite some time ago; perhaps it
is best to drop the build number entirely?
> Should I propose / check-in a patch to expose sys.build_info instead
> ("CPython", "41761", "trunk"), as this got positive feedback so far?
> It's also less surprizing than the current sys.build_number, which is a
> string despite its name.
Propose first. I have the feeling that the feature will change forth
and back if everybody gets to say something. I would call it
sys.svnversion (because that's what it is).
What to put in in case of tagged builds is then yet another question.
Regards,
Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4