Closed hugovk closed 2 years ago
@hugovk Amazing, these are exactly the kinds of things I was going to work out later. Thanks so much!
You're very welcome, happy to help out!
I'll post tomorrow about how to put it on PyPI. Any thoughts for a name? strava_py
?
(Side note: PyPI does name normalisation whereby dashes and underscores can be interchanged, and they show dashes by default, but both work. See for example https://github.com/pypa/setuptools_scm/ / https://pypi.org/project/setuptools-scm/ that as a project prefers underscores.)
Awesome, thanks again! Having given it a bit more thought, I think "stravavis" is a better name, as the package is focused on visualisation. There was some discussion about moving away from it being strava-centric, but I intend to create new visualizations from other data in the bulk export zip (not just gpx/fit activity files). So the package will be mostly aimed at Strava users, even if some of the visualisations still work with activity files exported from other sources. Let me know what you think.
This PR adds a CLI for creating visualisations, and puts it into an installable package, ready for distributions via https://pypi.org so it can be installed using pip. (I can help with how to do that later!)
First, I moved the
strava_py
directory into asrc
directory. This is commonly used for Python projects. The main benefits is to make sure when you're testing, you're testing against something that has been installed, and not something that happens to have the same directory name in your current dir. Much more:The way to install from source:
Or if you're developing,
-e
means an editable install, so you can make changes to your local source tree and they're reflected in what's run:Then I went for
strava_py
as the CLI name (this can be changed):Example run:
I'll also add a bunch of inline comments to explain what some things do, please feel free to ask more about any of this!