Hi Andrea, Thanks for your interest, I already accepted your first pull request. I am BCCing sphinx-dev and adding tinkerer-dev so we don't spam Sphinx users.
I am running unittest package with python -m tinkertest. I believe this only works with Python 3, which I am using for development, though I am trying to support everything from Python 2.6 up. I should indeed write these things somewhere, I'll put it on my ToDo list. Looking forward to your contributions going forward! Thank you, Vlad On Sun, Feb 26, 2012 at 10:27 AM, Andrea Crotti <andrea.crott...@gmail.com>wrote: > On 12/14/2011 11:13 PM, vladris wrote: > >> Hi, >> >> If anyone in the Sphinx community is interested, I just released the >> first version of Tinkerer which enables blogging with Sphinx. You can >> find more information on the Tinkerer website: http://tinkerer.me/. >> >> The project is still in beta so I appreciate your feedback. >> >> Thank you, >> Vlad >> >> > Very interesting Vlad, it might be finally a very good way to blog :) > > I forked your project and will try to contribute as soon as I start to use > it. > For example one thing which is a bit "dangerous" is that > tinker -s > will create the project files in the current directory, without asking for > any confirmation (not sure if it > overwrites if something already exists). > > I would take an optional argument with the destination, which defaults to > the current directory, but > ask confirmation in that case..It seems a bit safer.. > > And what do you use for running tests? (should be good to say that > somewhere). > With nosetests I get 4 failing tests with the latest revision.. > -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
