> Things will get worse with the 2.2a2 release, as there are a couple > of things that I definitely want in there that aren't finished yet, > so it'll be at least another week until I'm done, and moreover I'll > have to be making a few (minor) mods to files outside the Mac > subtree. =46rom a procedural, quality-guaranteeing point of view, I think you shouldn't release anything as "MacPython 2.2a2" which does not come from the 2.2a2 tag (and, as Guido explains, you should never move a tag). There is no such thing as the "Unix release" of Python 2.2a2; there is the source distribution, and there happens to be a Windows binary (which I trust came from the tagged source); everything coordinated by the release manager. IOW, if your changes missed the release date by a few days, tough luck - PEP 251 is there precisely for the purpose to align your changes with the rest of the tree, and to enable you to get a consistent, if not perfect, code base included in the alpha release. In theory, all you have to do is to compile this to get a binary distribution, perhaps with any add-on modules that you also want to distribute. It seems that nobody else is making much fuss about this, so I'll shut up now... 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