Scot Hacker

@Eccleshall @jrief Thanks for the confirmation! I can live with the workaround until the next release. Cheers!

How about "libpytunes" or "lib-pytunes" or "libtunes" or "tuneslib" or "itunes-lib" ? (I don't think it needs "py" in the name - obviously everything in pypi is python).

I'm doing some work on PEP-8 compliance now, which should land very soon. Please don't add to pypi until that's in, thanks. Probably also worth bumping the version number before...

So with the PEP8 done and with introduction of basic tests, are we ready to do the name change and get this into pypi?

Seems to be libpytunes - @liamks will need to rename the repository, if everyone is still in agreement on that?

Right on! Nice how github does the redirect automatically. But we'd better do a search/replace on the naming right away, as setup.py still installs the egg with the old name...

PR: https://github.com/liamks/libpytunes/pull/46 Current users will of course have to re-do their requirements and imports.

Out of curiosity, is Travis really a requirement for the pypi release? Doesn't seem like a blocker to me. We can always add Travis or other CI tool at any...

> We still need a branching strategy though, as we probably don't want every build of main going to PyPi. My recommendation would be to use git tags to record...

Merged. Next steps to getting this on pypi?