RDFLib/rdflibissueplayground — Issue #44: release 0.2
Author: gjhiggins
Created: 2012-02-20 05:28:55+00:00
State: open
Labels: open

gromgull, 2012-01-20T10:34:46.000Z
The SPARQL Result object change is not released - we should really release something so that we have a working match for rdflib 3.2.0

Some things to do before releasing:

* Commandline tools in rdfextras.tools => bin folder or setuptools console_script entry point
* README.txt could list the dependencies

Comment 1 by tak...@gmail.com
Also, we should have a shot at Python 3 compatibility. I'll try to look into this.

I submitted a patch for SPARQLWrapper, but I haven't had a response yet.

Comment 2 by tak...@gmail.com
My patch to SPARQLWrapper was accepted, and Sergio is talking about doing a release next week. I'll try to have a look at rdfextras over the weekend.

Comment 3 by gromgull
I merged the jsonld branch to have this included in the release.

Comment 4 by gromgull
Graham: Is there some good reason why the docs are in rdfextras/docs, not directly in / ?

Comment 5 by gjhigg...@gmail.com
+ Is there some good reason why the docs are in rdfextras/docs, not directly in / ?

None at all. They could migrate to the module root, no problem.

Comment 6 by gromgull
I've clobbered this now - I just removed all the manual plugin registration, now everything is done by setuptools entry points.

There is a fall-back rdfextras.registerplugins method in case of distutils:
http://code.google.com/p/rdfextras/source/browse/rdfextras/__init__.py#34

Unfortunately, we had forgotten entry-points for the query processor and results in rdflib - which I've now added:

http://code.google.com/p/rdflib/source/detail?r=d5d7a5b895601d62c2e5fa1e66915b556ba413b4

This means that if we release 0.2 now, it wont work with automatic registration with 3.2.0 ...

we could now push a 3.2.1 and have 0.2 depend on this, and it's all fine :)