Yesterday, I decided spend some of my time in a tinny tool created for me one year and half ago. This tool was named redmine-cmd and, obviously, the purpose of this tool is the usage of the Redmine ticketing system directly from the console system but also auto-submit the time expended in each task automatically.
The tool was functional with Redmine <=1.2 until now but it didn’t implement all the API definition covered by the latest versins of Redmine. The reason of that it was bacause the places where I was using this tool had not been upgraded to the latest version of Redmine for years. One of the consecuences of this was that many API/REST ending points was not be available for my tool in those early Redmine enviroments, therefore some relevant values related to a Redmine’s issue as the tracker id, the activity id or the issue status code wasn’t available to be obtained from the server causing, these restrictions, weird things like the definition of enumerators in the redmine-cmd configuration file with the same values that in the server.
But it’s a new time today, the time come down and the last Redmine with a version < 2.2 is not anymore around me so, yesterday, finally I decided end the integration with the Redmine API using the ending points required by my tool to get dinamically all the data required from the server:
The final implemantion is already available on PIP public repositories with MIT license to be used for everybody. The usage is quite trivial and the installation and setup steps are documented int the README file. Please, download and use it, any feedback will be welcome.
The quiz of this library is that it uses the quicksort (makes O(nlogn) comparisons to sort n items) algorithm.
From a couple of days ago, I has been recycling my knowledge about Debian-Python packages. Debian 6.0 is currently next to be released and we’ll need effort to adapt many of own packages from etch to squeeze.
I’ve been following the Debian-Python mailling list from one year ago and I know many several troubles, changes or improvements which was occurred during this period.
As a brief resume, many things has changed: default Python interpreter for Debian 6.0, the backend frameworks to build packages (CDBS with python-distutils.mk, Python-central or Python-support) …
I’ve been searching documentation about build a Command Line Interpreter (CLI) from some time ago. My requirements were:
I was needed a command history
I was needed TAB auto-completion.
… a easy framework.
Against I could expect, I didn’t found a lot of information on Internet about this aim. So after some time searching documentation about it, I had some luck and I finally found some refers to cmd Python module (oh, what surprise!):
Last week, I has been fighting against the hordes of the character encoding. My new task in tha job-tasks-pool is develop a friendly web app to manage configuration files of cluster apps. Ohh, great idea!, why didn’t I realize it before? (irony) . Only I need 4 things: one parser for each conffile syntax, a stable and secure way to get/save remote files, work with non-controlled kind of differents char encodings, … and a fancy GUI. As you can intuit, the task is not just a bit app, but this post only refer to a very useful python lib ( chardet discovered a few days ago. This lib can be auto-detect the encoding of a file very reliable. I suggest you that visit chardet homesite to see some clear examples.