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 edwardw
Recipients barry, edwardw, eli.bendersky, ethan.furman
Date 2018-06-27.07:15:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1530083740.13.0.56676864532.issue33976@psf.upfronthosting.co.za>
In-reply-to
Content
Ethan - thank you for your speedy response!

For an example you can see https://github.com/ucb-bar/hammer/blob/97021bc7e1c819747f8b8b6d4b8c76cdc6a488e3/src/hammer-vlsi/hammer_vlsi_impl.py#L195 - the ObstructionType enum is really only used inside PlacementConstraintType, so it was thought to be logical to nest ObstructionType inside PlacementConstraintType and reference it as PlacementConstraintType.ObstructionType.

It just seemed weird that inline class definitions inside an Enum get treated as an enum value while functions defined inside Enums are treated as methods - as a user it would make more sense to have them both treated the same way (not as enum values), I think.
History
Date User Action Args
2018-06-27 07:15:40edwardwsetrecipients: + edwardw, barry, eli.bendersky, ethan.furman
2018-06-27 07:15:40edwardwsetmessageid: <1530083740.13.0.56676864532.issue33976@psf.upfronthosting.co.za>
2018-06-27 07:15:40edwardwlinkissue33976 messages
2018-06-27 07:15:39edwardwcreate