add setup.py#2
Conversation
… Disable parse() hook on definition records by default.
…m. Added a few comments and TODOs.
…clude scaling if it's = 1. Added TODO comment.
…expected by the new profile.def.
… to be arrays were declared as such and would end up in a binary parse error. I'm not crazy about the fix, but justification is in comments.
…rom having namedtuples in the first place.
|
Hey Mitsukuni, Thanks for this. I will review and add a setup.py file this week! Thanks again, David On Saturday, December 31, 2011, Mitsukuni Sato <
David Cooper T:416.601.1999 x 223 |
|
Would be really nice to have this. Should be able to publish it to the Python Package Index http://pypi.python.org/pypi then to make it really easy for people to install it with pip or easy_install. |
|
setup.py added to my new branch (ng). |
Committing the work I've been doing over the past little while on a rewrite for python-fitparse. Major Changes ------------- * New, hopefully cleaner public API with a clear division between accessible and internal parts. (Still unstable and partially complete.) * Proper documentation! Going to use Sphinx. * Unit tests and example programs. * (WIP) Command line tools (eg a `.FIT` to `.CSV` converter). * Component fields and compressed timestamp headers now supported and not just an afterthought. Closes issues #6 and #7. * FIT file parsing is generic enough to support all types. Going to have specific `FitFile` subclasses for more popular file types like activities. * (WIP) Converting field types to normalized values (for example, `bool`, `date_time`, etc) done in a consistent way, that's easy to customize by subclassing the converter class. I'm going to use something like the Django form-style `convert_<field name>` idiom on this class. * The FIT profile is its own complete python module, rather than using `profile.def`. * Bonus! The profile generation script is less ugly (but still an atrocity) and supports every ANT FIT SDK from version 1.00 up to 5.10. * A working `setup.py` module. Closes issue #2, finally! I'll upload the package to PyPI when it's done. * Support for parsing one record at a time. This can be done using `<FitFile>.parse_one()` for now, but I'm not sure of the exact implementation yet.
|
Also, you should make sure you register the name fitparse on pypi so no-one else can. |
|
Would it be possible to also add a setup.py to the master branch? I would like to make use of your library but I'm having trouble getting the ng branch code to parse my FIT files (I guess the ng code is in a state of flux at the moment?) so I would like to make use of the old code for now. Thanks for devoting time to maintaining the library! |
Hi,
I add setup.py which is draft version of python-fitparse package.
Please fill setup.py with your information.