Python 3 compatibility in example scripts #49
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the python script patches, I'll test them and apply if no problem.
You can contact me via my email at the top of the pikrellcam .c source files.
…On Mon, 12 Aug 2019 16:56:54 -0700 David Christenson ***@***.***> wrote:
Python 2 will be retired in [less than 5 months](https://pythonclock.org/), and Python 3 is apparently the
default in [Buster](https://wiki.debian.org/Python#Supported_Python_Versions).
I'm also working on packaging this for Arch (where Python 3 has been the default for nearly a decade), and
this would be one less thing that I'd need to patch.
Note that I haven't tested these yet because I'm not currently using them, and I'm working on some other
things, but these were all the incompatibilities I noticed from reading the code, and as far as I know
everything should still work with Python 2.
P.S. I'd like to speak to you about some things regarding the Arch packaging, is there a good way for me to
contact you? Feel free to email me at the address in my profile if that's your preferred method and you'd
rather not share your address here. You can view, comment on, or merge this pull request online at:
#49
-- Commit Summary --
* Python 3 compatibility
-- File Changes --
M scripts-dist/ds18b20.py (21)
M scripts-dist/example-motion-detects-fifo (35)
M scripts-dist/example-motion-events (13)
M scripts-dist/example-motion-send-alarm1 (5)
M scripts-dist/example-motion-send-alarm2 (12)
M scripts-dist/pkc-alarm (6)
M scripts-dist/pkc-motion (16)
M scripts-dist/pkc-reboot (18)
M scripts-dist/pkc-recv (2)
-- Patch Links --
https://github.com/billw2/pikrellcam/pull/49.patch
https://github.com/billw2/pikrellcam/pull/49.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#49
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Python 2 will be retired in less than 5 months, and Python 3 is apparently the default in Buster.
I'm also working on packaging this for Arch (where Python 3 has been the default for nearly a decade), and this would be one less thing that I'd need to patch.
Note that I haven't tested these yet because I'm not currently using them, and I'm working on some other things, but these were all the incompatibilities I noticed from reading the code, and as far as I know everything should still work with Python 2.
P.S. I'd like to speak to you about some things regarding the Arch packaging, is there a good way for me to contact you? Feel free to email me at the address in my profile if that's your preferred method and you'd rather not share your address here.