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 eli.bendersky
Recipients barry, cool-RR, eli.bendersky, ethan.furman
Date 2014-09-28.12:39:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411907972.86.0.522541049541.issue22505@psf.upfronthosting.co.za>
In-reply-to
Content
>> I could continue the discussion about databases, but it feels like a waste of time to me. The main principle is: If something has an important property (in this case an enum object's numerical value), it should be publicly exposed. Period. No need to spend hours discussing if and how that property will be used. They always end up getting used somehow-- The only question is whether the people using them need to obtain them through private variables for years until the developers finally understand that the property needs to be exposed publicly. If you want to go through that, be my guest.


This kind of attitude is not welcome in the core Python development community. Please keep the discussion courteous and stick to technical arguments.

FWIW I fully agree with Barry and Ethan here.
History
Date User Action Args
2014-09-28 12:39:32eli.benderskysetrecipients: + eli.bendersky, barry, cool-RR, ethan.furman
2014-09-28 12:39:32eli.benderskysetmessageid: <1411907972.86.0.522541049541.issue22505@psf.upfronthosting.co.za>
2014-09-28 12:39:32eli.benderskylinkissue22505 messages
2014-09-28 12:39:32eli.benderskycreate