some maintenance questions
Thomas Vander Stichele
some random questions as I'm gearing up for a four day hacking session
that will involve a lot of Paisley.
1/ I like most of my projects to have an easy way to show test coverage.
Usually I integrate something like 'make coverage' into a Makefile and
it spits out a nice coverage report.
Is it ok to add a simple developer-oriented Makefile ?
If not, is there some standard way to integrate that in setup.py (a la
python setup.py coverage) ?
2/ Similar question, but for pep8 correctness and pychecker (disclaimer:
I comaintain pychecker)
3/ My main annoyance in paisley is CouchDB.bindToDB()
It magically removes the first argument from all subsequent calls at
runtime. I'm sure when that was added someone thought 'cool, I can
magically rewrite function arguments'. But I seriously dislike this
kind of magic morphing, and avoid it completely in all my paisley-using
code.
I personally think that if someone wants to do this kind of magic, (s)he
should just use a decorator.
Is this something we could deprecate then remove ? Or am I the only one
horrified ? :)
4/ paisley is a little lax about str vs unicode. I've been fixing bugs
randomly as I hit them, but I'd like to do a full pass so that I don't
have fixes like that in my feature branches. Since couchdb is fully
unicode in most places (except possibly db names, which have strict
naming rules), I think the API should just require and generate unicode
everywhere. Any opinions ?
Thanks
Thomas
--
--
There has to be a change, I'm sure
Today was just one day fading into the other
and that can't be what life is for
--
GStreamer - bringing multimedia to your desktop
http://gstreamer.freedesktop.org/
Thomas Vander Stichele
5/ anyone against putting all tests in paisley/test like it's done in
twisted ? Esp. with the .ini file it seems nicer to keep them apart.
6/ how about I set up a buildbot for paisley some time soon ?
Thomas
--
--
Don't you see that my heart's on fire
wicked wings that you spread round me sometimes
All I know is we've got to aim higher
Babe I wish that we'd go for the great escape
--
URGent, best radio on the net - 24/7 !
http://urgent.fm/
Thomas Vander Stichele
> 1/ I like most of my projects to have an easy way to show test coverage.
> Usually I integrate something like 'make coverage' into a Makefile and
> it spits out a nice coverage report.
>
> Is it ok to add a simple developer-oriented Makefile ?
>
> If not, is there some standard way to integrate that in setup.py (a la
> python setup.py coverage) ?
I went with a Makefile for now. If someone objects it can always be
reworked.
>
> 2/ Similar question, but for pep8 correctness and pychecker (disclaimer:
> I comaintain pychecker)
I added a pep8 one, but not a pychecker one yet.
> 4/ paisley is a little lax about str vs unicode. I've been fixing bugs
> randomly as I hit them, but I'd like to do a full pass so that I don't
> have fixes like that in my feature branches. Since couchdb is fully
> unicode in most places (except possibly db names, which have strict
> naming rules), I think the API should just require and generate unicode
> everywhere. Any opinions ?
I started a feature-unicode branch. It turns out there's an actual
bug/behaviour change in the C implementation of the json module; it
returns str for text when it can instead of unicode always.
simplejson has the same schizophrenic behaviour always. It may be
faster, but it seems to be incorrect to me.
I made a blog post here: http://thomas.apestaart.org/log/?p=1320
Let me know what you think about that particular issue...
Thomas
--
--
- You're a human ?
- Hardly. I'm a lawyer.
--
Moovida - future TV today !
http://www.moovida.com/
Thomas Vander Stichele
> Replying to myself, but ...
>
>
> 5/ anyone against putting all tests in paisley/test like it's done in
> twisted ? Esp. with the .ini file it seems nicer to keep them apart.
Did that too.
>
> 6/ how about I set up a buildbot for paisley some time soon ?
Did that too, couldn't sleep two nights ago.
First stab:
http://build.fluendo.com:8220/waterfall
Let me know if you want to run a slave.
Thomas
--
--
How close am I
to losing you ?
--
savon - Saving your work to svn
https://apestaart.org/thomas/trac/