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 jerome.hamm
Recipients benjamin.peterson, jerome.hamm, python-dev, vstinner
Date 2020-04-05.14:36:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586097420.08.0.530172689469.issue40174@roundup.psfhosted.org>
In-reply-to
Content
Yes, I get your meaning, and I totally agree with it, I was wondering what was the best way to do it, stay close to the cause, which would allow to more easily go along with changes, or put it in the configure file and warn the user as soon as possible... It was kind of a flip a coin decision in the end.

For my information, is there a kind of committee or someone taking these kinds of decisions or at least expressing rules as to the spirit in which they should be made?

On the same track, how can I find why someone wrote "
/* Various compilers have only certain posix functions */
/* XXX Gosh I wish these were all moved into pyconfig.h */
" in posixmodule.c? Is it just because no-one had the opportunity to do it and it is OK for me to do it?

"Fetchez la vache"
History
Date User Action Args
2020-04-05 14:37:00jerome.hammsetrecipients: + jerome.hamm, vstinner, benjamin.peterson, python-dev
2020-04-05 14:37:00jerome.hammsetmessageid: <1586097420.08.0.530172689469.issue40174@roundup.psfhosted.org>
2020-04-05 14:37:00jerome.hammlinkissue40174 messages
2020-04-05 14:36:59jerome.hammcreate