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 Devin Jeanpierre
Recipients Devin Jeanpierre, alex, brett.cannon, christian.heimes, gregory.p.smith, terry.reedy
Date 2017-09-08.21:05:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
So here's an interesting issue: oss-fuzz requires that the built location be movable. IOW, we build Python into $OUT, and then the $OUT directory gets moved somewhere else and the fuzz test gets run from there. This causes problems because Python can no longer find where the modules it needs are (encodings for example).

First thought: wouldn't it be nice if we could make a prepackaged and hermetic executable that we can move around freely?

Second thought: isn't that "Hermetic Python", as used within Google?

Third thought: doesn't Google have an internal fuzz testing environment we can use, instead of oss-fuzz?

So unless someone says this is a bad idea, I'd propose we not run these in oss-fuzz and instead run them in Google proper. The alternative is if there's a way to make it easy to move Python around -- is there a way to build it s.t. the import path is relative and so on?
Date User Action Args
2017-09-08 21:05:33Devin Jeanpierresetrecipients: + Devin Jeanpierre, brett.cannon, terry.reedy, gregory.p.smith, christian.heimes, alex
2017-09-08 21:05:33Devin Jeanpierresetmessageid: <>
2017-09-08 21:05:33Devin Jeanpierrelinkissue29505 messages
2017-09-08 21:05:33Devin Jeanpierrecreate