Skip to content
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

WIP: refactor to comply python3.8 and python3.9 #226

Draft
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

HerrMuellerluedenscheid

No description provided.

@resingm
Copy link

resingm commented Jan 5, 2021

Great to see, that someone's working on a compatible version for Python versions >3.8.
Any updates regarding this PR?

@HerrMuellerluedenscheid
Copy link
Author

I'm on vacation til the end of the week and will hopefully find the time to look into this next week. A few additional errors were raised within the unit test which I need to have a closer look at.

@pavandv
Copy link

pavandv commented Jan 9, 2021

Hey, just curious.. I'm eagerly waiting for this PR to be merged.. Is the PR ready to be merged?? Thanks

@HerrMuellerluedenscheid
Copy link
Author

It's not ready, yet. The tests do not succeed yet because of previously introduced hiccups that need to be resolved on master beforehand, I guess.

@HerrMuellerluedenscheid
Copy link
Author

Depends on #231

…s0, race conditions on detached sessions, eliminated set_exception on client disconnect tasks, a few debug log message isEnabledFor wrappers."

This reverts commit 1f5efd3.
@HerrMuellerluedenscheid
Copy link
Author

HerrMuellerluedenscheid commented Jan 10, 2021

Tests pass for python 3.6, 3.7, 3.8 and 3.9 after reverting as discussed in #231.
https://travis-ci.org/github/beerfactory/hbmqtt/builds/753846602.
Still, I would like to have #231 resolved to build on solid grounds.

@HerrMuellerluedenscheid HerrMuellerluedenscheid changed the title WIP: refactor to comply python3.8 WIP: refactor to comply python3.8 and python3.9 Jan 10, 2021
@pavandv
Copy link

pavandv commented Jan 19, 2021

Hey @HerrMuellerluedenscheid is this PR ready to be merged? I saw your other PR's (#228, #229) and Issue (#235) & I don't think @njouanin is ready to act on those..

If this PR is ready I would like to merge this into my own Fork.. Thanks.

@HerrMuellerluedenscheid
Copy link
Author

HerrMuellerluedenscheid commented Jan 20, 2021

Hey @HerrMuellerluedenscheid is this PR ready to be merged? I saw your other PR's (#228, #229) and Issue (#235) & I don't think @njouanin is ready to act on those..

If this PR is ready I would like to merge this into my own Fork.. Thanks.

Hey @pavandv ,
No, it's not ready. I mean tests pass but I reverted a commit by @shipmints in this MR just to get the CI running. Thus, this MR now additionally depends on #236 to restore what @shipmints fixed.
We need feedback/approval/merge by @njouanin.

@pavandv
Copy link

pavandv commented Mar 2, 2021

Hey @HerrMuellerluedenscheid as this is not maintained anymore, what is the status on this??

@FlorianLudwig
Copy link
Contributor

@pavandv hey,

i continued the branch there: Yakifo/amqtt#18

it does not contain changes compared to this branch for the actual code, just tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants