-
Notifications
You must be signed in to change notification settings - Fork 54
PyPi package #34
Comments
https://pypi.org/project/pytuya/ posted by https://github.com/sean6541 - current version 7.0, so to avoid issues initial version needs to be (at least) 7.0.1 to ensure an upgrade will work (need to check code level used, incase API different in which case a major version bump required, https://semver.org/) |
My biggest problem is currently the package name :-) as pytuya is already used by @sean6541. We could definetly ask sean6541 to hand over the maintenance to us. But I think there might already be software out there which uses the package and I don't want to continue the version numbering (it's already 7.0). What do you think, @clach04 ? Do you have any preferences? |
@Exilit no strong preferences on my part. What are your thoughts on the versioning, what would you like to see? I was about to add a version to the module then saw your comment, so I held back :) |
Using 7.0.1 to be slightly ahead of https://pypi.org/project/pytuya/
@Exilit new version posted to pypi, under pytuya name with current code. Outstanding things to resolve:
Currently the setup.py file has a dependency on pyaes. This works things that are not perfect about this setup:
Leaving open for discussion for a while. |
Package available from https://pypi.org/project/pytuya/
Related to Issue #24.
If any one is interested and has not worked on PyPi support before, I have a sample project at https://github.com/clach04/x10_any (sadly I don't have "how to publish" notes there, from memory I used twine but I did bookmark https://nosarthur.github.io/coding/2018/07/01/pypi.html which has a note on how to use a Markdown formatted readme that I mean to try).
Random thoughts:
obviously need a setup.py :) (see x10_any)commit 92873a2Need a version string to be added (see x10_any)commit ed44ab9The text was updated successfully, but these errors were encountered: