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 loewis
Recipients chris.jerdonek, ezio.melotti, loewis, ncoghlan, pitrou, r.david.murray
Date 2012-10-25.20:43:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351197833.66.0.7521685809.issue15494@psf.upfronthosting.co.za>
In-reply-to
Content
This may increasingly get off-topic, so I'll stop with generalities after this post.

I find the effect of modularization on discoverability to be two-sided.

On the one hand, splitting functionality into groups helps discoverability, since you don't have to wade through tons of API, and the risk "to see but not to recognize" is reduced.

OTOH, the risk of entirely ignoring some functionality because it is placed somehwere where you wouldn't expect it is increased. The classical example is the the gethostname() function, which many people wouldn't expect in the socket module.

I have personally given up on expecting "logical" grouping when trying to find functionality (not just in Python, but in general). Instead, I rely on full-text search, which works reasonably well these days. I do use modularity when studying "close friends" related to some API I already know.
History
Date User Action Args
2012-10-25 20:43:53loewissetrecipients: + loewis, ncoghlan, pitrou, ezio.melotti, r.david.murray, chris.jerdonek
2012-10-25 20:43:53loewissetmessageid: <1351197833.66.0.7521685809.issue15494@psf.upfronthosting.co.za>
2012-10-25 20:43:53loewislinkissue15494 messages
2012-10-25 20:43:53loewiscreate