This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author televi
Recipients dstufft, eric.araujo, jkloth, televi
Date 2020-03-18.21:59:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In looking through the file for uvloop, I see that they purposely do not call super().initialize_options() or super().finalize_options() in their code if they've already been called once.

I think that is why their code is revealing this problem - the 2nd command to be run is inheriting the self.compiler value from the first command since build_ext.initialize_options() isn't being called to (re)set self.compiler to be None.

I'm not sure if there's a "rule" that says each command must call initialize_options() to "sanitize" the object or not but that does explain why the 2nd command is seeing a CCompiler object() for self.compiler on the 2nd time through.
Date User Action Args
2020-03-18 21:59:51televisetrecipients: + televi, jkloth, eric.araujo, dstufft
2020-03-18 21:59:51televisetmessageid: <>
2020-03-18 21:59:51televilinkissue39917 messages
2020-03-18 21:59:50televicreate