Comments on: Python Libraries http://jessenoller.com/2006/03/01/python-libraries/ python, programming and other things Thu, 24 Jul 2008 05:34:31 +0000 http://wordpress.org/?v=2.5.1 By: TML http://jessenoller.com/2006/03/01/python-libraries/#comment-20 TML Fri, 08 Sep 2006 00:07:04 +0000 http://jessenoller.com/2006/03/01/python-libraries/#comment-20 It doesn't sound like such a document exists. Perhaps you could write down the things in your own head and start the ball rolling?<br /><br />Personally, I always feel like I'm probably structuring my code in a way that no one but me will ever understand. :) It doesn’t sound like such a document exists. Perhaps you could write down the things in your own head and start the ball rolling?

Personally, I always feel like I’m probably structuring my code in a way that no one but me will ever understand. :)

]]> By: chrism http://jessenoller.com/2006/03/01/python-libraries/#comment-19 chrism Wed, 06 Sep 2006 16:58:13 +0000 http://jessenoller.com/2006/03/01/python-libraries/#comment-19 Packaging/installation with distutils.<br /><br />Advertising via cheese shop.<br /><br />Spells out clearly what its platform limitations are.<br /><br />Has narrative documentation describing how someone might actually use it in the real world.<br /><br />If a library calls into code that its end user writes, it's not a library, it's a framework. If it has its own mainloop, it's an application, not a library. Packaging/installation with distutils.

Advertising via cheese shop.

Spells out clearly what its platform limitations are.

Has narrative documentation describing how someone might actually use it in the real world.

If a library calls into code that its end user writes, it’s not a library, it’s a framework. If it has its own mainloop, it’s an application, not a library.

]]> By: Marius Gedminas http://jessenoller.com/2006/03/01/python-libraries/#comment-18 Marius Gedminas Wed, 01 Mar 2006 16:42:30 +0000 http://jessenoller.com/2006/03/01/python-libraries/#comment-18 Using easily-googlable, non-generic package name: good idea.<br/><br/>Adding a README.txt with doctest sections as a usage guide: very very good idea. (Examples: <a HREF="http://source.schooltool.org/svn/trunk/schooltool/src/schooltool/relationship/README.txt" REL="nofollow">schooltool.relationship</a>, <br/><a HREF="http://svn.zope.org/Zope3/trunk/src/zope/formlib/form.txt?rev=41757&view=markup" REL="nofollow">zope.formlib</a>.) Using easily-googlable, non-generic package name: good idea.

Adding a README.txt with doctest sections as a usage guide: very very good idea. (Examples: schooltool.relationship,
zope.formlib.)

]]>