Given that Python 2.6 just hit its final beta, wouldn't it make sense to target that instead? Or is 2.5 all ready to go pending this ARC case, while 2.6 would take another couple months to wait for release, complete testing, etc?
> Projects delivering Python modules are advised to deliver them > for both Python 2.4 and Python 2.5. Is there a requirement to deliver them for one version or the other? If "both" is merely advisory, then one team may deliver for one version, another for the other version, and anyone wanting to use those modules will be unable to use both. Perhaps there should be a requirement for 2.5 modules? Or just make both required for the time being? > Projects delivering shared object Python modules are advised to > deliver both 32 and 64-bit versions, as per PSARC/2006/666 Same issue here, too. Though the way this is worded suggests that the word "shared" is missing from the 2.4/2.5 paragraph. Projects delivering Project Private modules can presumably do whatever they want. Danek
