I'm in a quandry about the patch implementing PEP 229. The patch is quite close to being ready, with only a few minor issues remaining, but to fix those issues, I need to make some changes to the Distutils, such as the sysconfig modification I recently suggested. Problem: I believe the patch *must* go in at the alpha stage, because there are bound to be lots of platform-specific problems that will show up; it should not be added in the beta stage, because it'll need time to get tested and debugged, and I wouldn't be surprised if it has to be reverted later because of some insurmountable problem. Problem: Greg Ward, the Distutils maintainer, is away at the moment. I can check in changes to the Distutils without his say-so, but when Greg gets back he might shriek in horror and rip all of the changes out again. (Or he's stuck with maintaining them until 2.2.) Problem: 2.1alpha1 is due on Friday. So, what to do? If I know there's going to be an alpha2, that's probably fine; Greg should have resurfaced by then, and the patch can go in for alpha2. Or, I can check in the changes before Friday, and if they're unacceptable, they can be fixed for alpha2/beta1, or simply backed out. Or, I can leave Distutils alone and make setup.py a tissue of hacks and workarounds. For example, it might insert new versions of various functions into the distutils.sysconf module. Icky and fragile, but cleaning it up for beta1 would then be a priority. Suggestions? Pronouncements? --amk
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