-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 missing import in socketrpc.py (branch 0.8) #681
Conversation
0.8 is a release branch... this has already been taken care of in master (the rpc code was removed) |
if the |
the rpc code has already been removed in master and this change will go out in the next release. |
so this next release, is it a new major version from the master branch? e.g. 1.0 .1 i can see the 0.8.1 version installed by |
Locust doesn't really have a release cadence or an established release plan.
The last few were cut from release candidate branches tagged from master.
Once tagged and designated a release, a tarball is uploaded to PyPI (which
is the official release channel).
…On Sun, Nov 12, 2017 at 6:48 PM, 叶泽宇 ***@***.***> wrote:
so do you release a new major version from the master branch? e.g. 0.9 .1
or do you release a new minor version from the master branch? e.g. 0.8.2
i can see the 0.8.1 version installed by pip install locustio has the
same code as the 0.8 branch
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#681 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABD7-cLnZeoHoSFzDxRP68tXvUh-siYUks5s14O-gaJpZM4QbDeD>
.
|
so are we gonna leave branch |
The 0.8 version has a dependency on Therefore the real issue is how that can happen in the first place. |
@heyman, if you want to know how this can happen in the first place, you can check this thread #302, there's an edge case for alpine (when here's also an example https://github.com/Shuliyey/locust-docker (that demonstrates The purpose of this pull request is to raise the fact that in |
Issue
This pull-request is to branch
0.8
.Locust pure python RPC not working in distributed mode (this makes, message seem confusing) - (#680)
Currrent/Expected Behaviour
pure Python socket RPC implementation works (when
pyzmq
is not installed/detected)Previous Behavour
pure Python socket RPC implementation doesn't work (when
pyzmq
is not installed/detected)