I added a blue print. does launchpad have a wiki? should we set one up? we could use openplans if yall like.
https://blueprints.launchpad.net/rdflib/+spec/split-major-packages <snip /> > > The pluggable architecture could if possible not *depend* on > setuptools, but use it if available. So the internal plugin registry > can be the same as today (used by setuptools if there or perhaps by > "manual" glue code if not..). Though practically it could be easier to > accept the setuptools dependency and "egg orientation" -- and I > suspect the namespace mechanism requires it.. (Note that the rdflib > namespace would be for project-owned code only (the "partitioned" > rdflib); 3rd party stuff can use the entry-point mechanism but should > have their own top-level package names.) the work I've done so far leaves the old plugin system pretty much intact for backward compatibility. re: reorging the packages RDFLib == rdflib.core RDFLibStore == rdflib.store RDFLibSPARQL == rdflib.sparql the one thing that come to mind is that we will need to make a bunch of module aliases to provide bw compatibility. we can still ship an RDFLib package that has all three, just now folks would have the option of installing and using them independently. -w -- | david "whit" morriss | | contact :: http://public.xdi.org/=whit "If you don't know where you are, you don't know anything at all" Dr. Edgar Spencer, Ph.D., 1995 "I like to write code like other ppl like to tune their cars or 10kW hifi equipment..." Christian Heimes, 2004
_______________________________________________ Dev mailing list Dev@rdflib.net http://rdflib.net/mailman/listinfo/dev
