Message137703
regarding "hey this is an MS bug not Python", projects which feature optional C extensions are starting to apply workarounds for the issue on their end (I will need to commit a specific catch for this to SQLAlchemy) - users need to install our software and we need to detect compilation failures as a sign to move on without it. I think it's preferable for Python distutils to work around an MS issue rather than N projects having to work around an MS issue exposed through distutils. Seems like this bug has been out there a real long time...bump ? |
|
Date |
User |
Action |
Args |
2011-06-05 15:40:55 | zzzeek | set | recipients:
+ zzzeek, loewis, mark.dickinson, giampaolo.rodola, schmir, tarek, eric.araujo, r.david.murray, srid, skrah, ipatrol, MrWerewolf, thorsten.behrens |
2011-06-05 15:40:55 | zzzeek | set | messageid: <1307288455.23.0.76803638165.issue7511@psf.upfronthosting.co.za> |
2011-06-05 15:40:54 | zzzeek | link | issue7511 messages |
2011-06-05 15:40:54 | zzzeek | create | |
|