search

Letractively / rdflib

Automatically exported from code.google.com/p/rdflib
Other
0 stars 0 forks source link

Fully document interface #120

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Clean up and fully document interface. Currently the interface and various 
plugin implementations 
are intermixed; the interface is easier to define and document if we separate 
one from the other. 
Also, we could benefit from defining __all__ in the interface modules to future 
clarify what's part of 
the interface vs. an implementation side effect (see the email package in the 
standard library for an 
example of this).

Original issue reported on code.google.com by eik...@gmail.com on 13 Feb 2010 at 1:26

GoogleCodeExporter commented 9 years ago 
See r1853 ( Still working on that commit syntax to associate commits with 
issues. )

Original comment by eik...@gmail.com on 13 Feb 2010 at 1:31

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r1854.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 13 Feb 2010 at 1:54

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r1855.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 13 Feb 2010 at 1:56

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r1856.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 13 Feb 2010 at 1:56

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r1857.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 13 Feb 2010 at 1:57

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r1858.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 13 Feb 2010 at 2:08

GoogleCodeExporter commented 9 years ago

Original comment by eik...@gmail.com on 13 May 2010 at 6:17

GoogleCodeExporter commented 9 years ago 
FYI, narrative doc update and location for API docs:

    http://groups.google.com/group/rdflib-dev/browse_thread/thread/40db2db4b18e3c3c?hl=en

Original comment by eik...@gmail.com on 5 Aug 2010 at 4:25

GoogleCodeExporter commented 9 years ago 
To re-create epydoc API docs, install epydoc and use the following command-line 
instruction to create a set of rdflib API docs in the directory "./apidocs" 
(relative to cwd):

$ epydoc -v --output apidocs --docformat reStructuredText --html rdflib

Original comment by gjhigg...@gmail.com on 6 Aug 2010 at 12:03

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision e86fcea8fc5f.

Original comment by eik...@gmail.com on 30 Mar 2011 at 9:06

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 9cbaa1d5de01.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 30 Mar 2011 at 9:06

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 1480ab5d132b.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 30 Mar 2011 at 9:06

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 78f72629e169.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 30 Mar 2011 at 9:06

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision b4843c5dc8d1.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 30 Mar 2011 at 9:07

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 6b55d87f14cf.

Moving parsers and serializer implementations into rdflib.plugins package

Original comment by eik...@gmail.com on 30 Mar 2011 at 9:07

GoogleCodeExporter commented 9 years ago 
Added __all__ lists to every source file. This broke the Py3.2 tests 
comprehensively, so I commented them out. I grepped the __all__s into a 
separate file -- see attached.

Original comment by gjhigg...@gmail.com on 16 Jan 2012 at 12:45

Attachments: