-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix #244] Fix incompatibilities with python3 #273
Conversation
@rlogiacco @MarcusWolschon folk, do you know someone, who can review this. |
@szobov I have this successfully working with OctoPrint 1.4.0 and Python 3.6.8. |
bump |
This doesn't seem to be working on Octoprint 1.4.0 + Python 3.7.3. Error:
I installed this through an archive the master branch of fork. |
Hi @goncalossilva ps; really don't like how the folk from python foundation deal with compatibility. :( |
@goncalossilva i've just updated PR. I've also pushed changes to the fork's master, so you can try just reinstall. |
@giloser may I ask you to review this changes, please |
Thanks @szobov! Confirmed working on Octoprint 1.4.0 + Python 3.7.3. |
You know, folk, it seems like this project is abandoned. : |
@szobov It does seem to be abandoned. Are you volunteering your fork? ;-) |
@ctgreybeard I don't really like to create to simultaneously living independent versions. I wish to hear from this project maintainers, that they don't want to maintain it anymore. |
@giloser ping |
Hi! sorry it take so long. I cannot accept this as this dropped python2.* compatibility which is not acceptable for all the people that still work on python2. I know some of the developer worked on this but I don't know the status. Sorry |
@giloser thank you a lot for the replay, I appropriate it. But what do you feel about my suggestion here: If you don't share my idea, we can close this PR and I can just maintain my fork for people, who are ok with pyhon3 only. Cheers. |
This is broken again on 1.4.2. It'd be nice to rebase, or at least cherry pick #270. |
22f1422
to
4bfbb9b
Compare
@goncalossilva I've fixed it, thanks for this catch. Btw, @giloser I'll abandon this MR, because it's really unpleasant to fix all conflicts after applying 2to3 and moving on python3. Thanks everyone, who helped with testing. I'll cherry-pick or just merge only most important changes in my fork. Cheers |
It might be worth to apply 2to3, and then fix it once to work with both python 2 and 3.
|
Hey @guysoft May I ask you to prepare this changes and maybe push it in my branch or file and send me a patch with changes which I could apply. Thanks for the understanding, |
Hey @donvito4ever |
Yes... I install from this link: and from this other: Same result... |
Yes, you've installed from the release, not with the changes from this PR.
Or you can install from the sources using this branch:
|
Thanks for your work @szobov |
Thanks @szobov , your version works for me with octoprint 1.4.2 and the octorprint python3 script update. |
I installed from https://github.com/szobov/OctoPrint-Telegram/archive/master.zip succesfully and notifications are send, but the emoticons are not working. They show:
|
Never mind. After upgrading Octoprint to Python 3, it works just fine ;-) |
I will re-open it soon with python2 compat |
❗ :ATTENTION: in this changes I've dropped python2.* compatibility,
And I also checked only with
OctoPrint 1.4.0
andPython 3.6.9
, so I'd appropriate if someone could test it.Closes #244
Thanks.