Daniel Krech a écrit : >>> These all look like great goals. I think they probably could be done >>> on trunk (where all the dev work is currently being done). >> Ok then. I think I'll be able to start this WE.
Hi all, As said earlier, I started to clean the trunk yesterday. I have trimmed all the trailing white spaces and set the svn:eol-style property to "native" on all source files so that windows developers have \r\n and unix developers have single \n chars instead. Please set up your svn client to use autoprops such as "* = svn:eol-style=native" to automatically add the property on newly checked in files. I also started the pep8/257-ification of the source code (currently just Graph.py) to respect standard python coding guidelines and make external devs feel at home when browsing the source code. Please respect the 79 chars by line rule that makes it much easier to read complex pieces of code. I hope I did not break anything. The test suite results do not seem affected by my changes. However the tests are really slow to run and looks like some of them rely upon an internet connection and a MySQL DB. I think it would be a good idea to separate fast running independent unit tests suite from slower running integration tests that need to setup external resources such as a broadband connection or a MySQL db. Furthermore, it would be interesting to use another setup to run bench tests such as the one used by the lxml project: http://codespeak.net/svn/lxml/trunk/bench.py Bench test should output results on stdout whereas unit test and integration tests should not (except when the fail) IMHO. I plan to further work on code style next week and later on the tests setups. Any comments welcome. Regards, -- Olivier _______________________________________________ Dev mailing list [email protected] http://rdflib.net/mailman/listinfo/dev
