Closed tnorth closed 11 years ago
Hmm my bad, the egg-info file seems to indicate that it is version 0.1 However, it is not tagged in the source tree.
It's because I haven't released a 0.1 yet. The version indicated in the repository is the one being prepared, not the last one being released.
Pyinsane seems pretty stable (except when the application stops, but it's not a blocking issue), so I guess I could tag a 0.1. I'll do it asap (probably this week-end).
By the way, I assume you will also need a released version for Pyocr ?
Ok thanks. Yes, I am working on it too...
Please leave this bug report open until I release a 0.1. It's a good way for me to keep this task in mind. :)
Sorry, wrong button and then I didn't want to add noise here again :)
Since the code seems stable and complete enough, I've bumped directly the version v1.0. A Git tag has been added.
Hi!
I am thinking of packaging paperwork, which requires pyinsane. To package the latter, it would be nice to have a version number or a versionning scheme. Any hint ?
Thanks,