your library supports an integration in Home Assistant, I would like to use your library in my Gentoo Overlay for Home Assistant, hope you don't mind.
1) Therefore I would need a release file either at Pypi in SDIST format, or as a tar.gz on github. I cannot use the library in wheel format. Normally, when no SDIST can be found at Pypi, I would take the source from Github. This was not possible in this case, because you do not tag releases here. A release on Github is OK, but a Pypi SDIST tar.gz release would be preferred, because this could take use of Gentoo's mirror system and updates download stats. Most of the other (~1100) integrations I use for the repo have both. If something goes wrong with one version, I would have the change to try the other. This could avoid holdups if other libraries depend on it.
2) Please add a tag for 0.1.6. As soon as you add a tag, Github builds a usable source archive. Make sure that release points in Github are on the commit which was used for the release in Pypi.
3) If you build an SDIST for Pypi, make sure that all files needed for building are included. A common mistake is a missing requirements.txt or README.md which the is opened by setup.py during compile process.
4) One or more of the requirements of this library are pinned to a specific version. Hard pinning may work now, but will lead to problems if an other integration updates it's requirements. To avoid future issues it would be good if this library would change its pinning to allow any higher version and just set a minimum version. Especially when you pin very common libraries like aiohttp or requests-oauthlib.
Thanks a lot for your work.
Thanks.
your library supports an integration in Home Assistant, I would like to use your library in my Gentoo Overlay for Home Assistant, hope you don't mind. 1) Therefore I would need a release file either at Pypi in SDIST format, or as a tar.gz on github. I cannot use the library in wheel format. Normally, when no SDIST can be found at Pypi, I would take the source from Github. This was not possible in this case, because you do not tag releases here. A release on Github is OK, but a Pypi SDIST tar.gz release would be preferred, because this could take use of Gentoo's mirror system and updates download stats. Most of the other (~1100) integrations I use for the repo have both. If something goes wrong with one version, I would have the change to try the other. This could avoid holdups if other libraries depend on it. 2) Please add a tag for
0.1.6
. As soon as you add a tag, Github builds a usable source archive. Make sure that release points in Github are on the commit which was used for the release in Pypi. 3) If you build an SDIST for Pypi, make sure that all files needed for building are included. A common mistake is a missingrequirements.txt
orREADME.md
which the is opened bysetup.py
during compile process. 4) One or more of the requirements of this library are pinned to a specific version. Hard pinning may work now, but will lead to problems if an other integration updates it's requirements. To avoid future issues it would be good if this library would change its pinning to allow any higher version and just set a minimum version. Especially when you pin very common libraries likeaiohttp
orrequests-oauthlib
. Thanks a lot for your work.\B.