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

doc updates for main class change from Locust to HttpLocust #116

Closed
zerog2k opened this issue Dec 4, 2013 · 5 comments
Closed

doc updates for main class change from Locust to HttpLocust #116

zerog2k opened this issue Dec 4, 2013 · 5 comments

Comments

@zerog2k
Copy link

zerog2k commented Dec 4, 2013

Looks as if very recently the main class was changed from Locust to HttpLocust.

Please update docs, and main website examples.

Update:
Ok, as I take a closer look at the api docs, perhaps a recent change was such that I could no longer access self.locust.host (i.e., the host param set on the cmdline).
I had to change main class from Locust to HttpLocust in order to access this.

@zerog2k zerog2k closed this as completed Dec 4, 2013
@heyman
Copy link
Member

heyman commented Dec 4, 2013

Hi!

The latest-version of the documentation should be updated, but I might have missed some place :).

I'll update the main website examples as soon as we release the 0.7 version (should be very soon hopefully).

@TTimo
Copy link

TTimo commented Dec 26, 2013

Ouch. I was coming here with this problem the other way. The documentation refers to HttpLocust, but the correct import is Locust (grabbed latest release from pip).

@heyman
Copy link
Member

heyman commented Jan 16, 2014

Ah, it would probably be nice to provide visitors with a version choice page when coming to http://docs.locust.io where it clearly asks users to select if they want the documentation for the latest (git) version, or the latest released version.

@TTimo
Copy link

TTimo commented Jan 16, 2014

Only the git code worked for me, the released versions relied on old dependencies that were no longer available or incompatible for me. Think a new release is in order :)

@heyman
Copy link
Member

heyman commented Jan 20, 2014

A new release is now up on PyPI :).

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

No branches or pull requests

3 participants