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 JBernardo
Recipients JBernardo, Jim Fasarakis-Hilliard, eric.araujo, eric.snow, maker, rhettinger, sbt, serhiy.storchaka, steven.daprano, terry.reedy
Date 2017-04-05.14:19:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491401963.32.0.126485128745.issue13290@psf.upfronthosting.co.za>
In-reply-to
Content
Being the OP, at that time I felt it was important to have a vars() function that worked on __slots__ to ease something I was developing. The truth for me is: __slots__ is not really relevant anymore. The benefits it brings are not enough to make the feature usable because of these incompatibilities with normal classes. Also, it does not bring real benefits even for most people who think they need this.

If you believe having vars() working on __slots__ is bad because people may want to update it, why would locals() exist at all?

Also, your argument that having vars() working on __slots__ classes may mask the wrong use of the attribute, why would someone use vars() on __slots__ if it doesn't work right now? If it is not useful for identifying this problem now, then I am ok with it not being useful in the future as well.

On any case, feel free to mark this as "rejected" or "wont fix" because if in 6 years no one cared enough to have it working means that either it is not important and/or __slots__ classes are also not relevant for others as well.
History
Date User Action Args
2017-04-05 14:19:23JBernardosetrecipients: + JBernardo, rhettinger, terry.reedy, eric.araujo, steven.daprano, maker, sbt, eric.snow, serhiy.storchaka, Jim Fasarakis-Hilliard
2017-04-05 14:19:23JBernardosetmessageid: <1491401963.32.0.126485128745.issue13290@psf.upfronthosting.co.za>
2017-04-05 14:19:23JBernardolinkissue13290 messages
2017-04-05 14:19:23JBernardocreate