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 orsenthil
Recipients docs@python, orsenthil, sandro.tosi, techtonik
Date 2011-03-11.09:25:22
SpamBayes Score 0.0015185116
Marked as misclassified No
Message-id <1299835523.91.0.307201753773.issue11009@psf.upfronthosting.co.za>
In-reply-to
Content
splituser is an internal API. It has never been exposed through Docs anytime and there are good reasons for that too. We never want internal helper functions (even tough they don't startwith _) be exposed through docs as it may clutter the API Documentation. 

If you find a good use for splituser like function, it would good to discuss and build upon current one before exposing. 

I am closing this as wontfix.
History
Date User Action Args
2011-03-11 09:25:23orsenthilsetrecipients: + orsenthil, techtonik, sandro.tosi, docs@python
2011-03-11 09:25:23orsenthilsetmessageid: <1299835523.91.0.307201753773.issue11009@psf.upfronthosting.co.za>
2011-03-11 09:25:22orsenthillinkissue11009 messages
2011-03-11 09:25:22orsenthilcreate