-
Notifications
You must be signed in to change notification settings - Fork 1
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
Updating README file on installation for new qibotn users #76
Updating README file on installation for new qibotn users #76
Conversation
Notice that using Poetry is only relevant to use it for development. Otherwise, |
Hi thanks @alecandido, thank you! Just wanted to put it out there because I faced the issue. Thanks a lot for sharing the work around of using pip install -e for dev purposes instead of poetry. |
You're welcome :) And I'm not opposing the change in the README (though I start wondering if we should keep this kind of information in the README in general). I.e. by calling |
@alecandido Right, I understand. If at all it's indeed information that we want to keep on the README file, it could probably be under a heading called "How to Contribute" instead of "Installation" then because this only for development purposes. But it any case, this information is found in the documentation of qibotn. Thank you for your insights on pip install -e. That was good to learn! |
@NithyasriVS, @Vinitha-balachandran we are planning to make a new release later this week. May I ask you to create a new section in the README and move these changes there? For the general user, the installation instruction should be |
Hi @Vinitha-balachandran , @scarrazza, I have changed it to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
To help new users of qibotn to install qibotn in the right manner since qibotn no longer uses
pip install .
for installation after the release. Changing the directions for installation in the readme file to the following