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 pfalcon
Recipients ncoghlan, pfalcon, serhiy.storchaka, terry.reedy
Date 2014-04-13.15:29:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397402997.32.0.170811698578.issue21180@psf.upfronthosting.co.za>
In-reply-to
Content
@Terry J. Reedy:

Thanks for the pointer. My inital response is <sadness>, another bloating of namespace. But I'm adjusting.

But that PEP shows the issue with all that activity: CPython stdlib got so big and bloated, that it lives its own life and people consider it normal. So, there're PEPs to perfectalize bytearray, without paying attention to the fact that array.array('B') is pretty much the same thing, but apirots (cf. bitrot) behind it.

So, following PEP467, this request should be updated to call for array.array.zero(typecode, size) factory method. Note that it would need to take 2 arguments to follow array.array API. Is that good or bad? IMHO, not much worse than introducing separate factory method at all. But again, author of PEP467 should rather consider how those proposals extend to other related types.

If you participate in the discussion of the PEP, I'd appreciate if shared there link to this ticket - I'm not in loop of general CPython development and have limited resources to learn/follow them. Thanks.
History
Date User Action Args
2014-04-13 15:29:57pfalconsetrecipients: + pfalcon, terry.reedy, ncoghlan, serhiy.storchaka
2014-04-13 15:29:57pfalconsetmessageid: <1397402997.32.0.170811698578.issue21180@psf.upfronthosting.co.za>
2014-04-13 15:29:57pfalconlinkissue21180 messages
2014-04-13 15:29:56pfalconcreate