Skip to content

Conversation

@nitrag
Copy link

@nitrag nitrag commented Oct 22, 2018

This will rename all module references of async to twisted to be compatible with Python 3.7+.

I ran the tests but I think the SSL ones failed. Please run your own tests before merging.

Resolves #46

@nitrag
Copy link
Author

nitrag commented Oct 22, 2018

@nikipore Is this what you were looking for in a PR?

@nikipore nikipore added this to the 2.4 milestone Oct 25, 2018
@nikipore
Copy link
Owner

Yes it is, thank you.

I am way too busy right now (job and kids), plus I am going to be on vacation, so a proper test and package before end-of-year might be a problem. This is a backwards-incompatible change, so I am going to bump the release to 2.4.

Time that someone else takes over this project, it has no longer relevance for my daily work, although I am still at the same company (but have moved on to other missions and no longer program myself on the job).

0. I still do accept (and test) pull requests and bugfixes (if they come with complete and working unit and integration tests), but the Python 3 port was my last big effort for stompest.
1. I believe that fully implementing the (half-complete) SSL/TLS capability is the most urgent enhancement because apart of that I consider stompest pretty much feature complete and very stable up to Python 3.6; the rate of newly discovered bugs is very low indeed.
2. For Python 3.7, the `stompest.async` package must be renamed; I believe `stompest.twisted` would be appropriate. If someone creates a pull request, I'll test it and rename the PyPI package accordingly.
2. For Python 3.7, the `stompest.twisted` package must be renamed; I believe `stompest.twisted` would be appropriate. If someone creates a pull request, I'll test it and rename the PyPI package accordingly.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revert this auto-replacement

@muhammadyibr
Copy link

@nikipore were you able to get sometime to merge this request? Seems good to me

@abompard
Copy link

I'm also interested in getting this to work, STOMP libraries for Python are kinda scarce.

@nikipore
Copy link
Owner

Sorry guys, I am entirely immersed in job and family. Don't know when or whether I'll find the time to adopt this.

Problem is, I've got to set up everything from scratch, and this will be a breaking change, meaning that I will probably have to deprecate the PyPI package stomp.async and create a new one stomp.twisted.

Still no-one interested in taking over and starting a new fork? I'd be willing to pass the control of the PyPI packages. This is how I got hooked by @theduderog years ago ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants