-
Notifications
You must be signed in to change notification settings - Fork 16
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
Broken installation (both via PyPi and GitHub) #26
Comments
Because there was not release after the rename, you should be able to still do
If the issue is that a release should be done, maybe you can argue for this in a new issue. Let me know if this does not solve your problem and this issue should be reopen. |
Hi @1ucian0 Thanks for the quick reply.
This would be great to provide in the README. Otherwise, I'm not sure if it would be possible for users to be aware of this. Perhaps this is obvious to those internally, but for me, this was definitely a surprise :) Regarding being able to use the package, I have a question about usage. I see that the import os
from qiskit.providers.honeywell import Honeywell
USERNAME = os.environ.get("QUANTINUUM_USERNAME")
PASSWORD = os.environ.get("QUANTINUUM_PASSWORD")
Honeywell.save_account(USERNAME,
proxies = { 'urls': {'http':
f'http://{USERNAME}:{PASSWORD}@qapi.quantinuum.com/',
'https':
f'http://{USERNAME}:{PASSWORD}@qapi.quantinuum.com/'
} })
backends = Honeywell.backends()
backend = Honeywell.get_backend(machine) However, this seems to fail is appears to be pointing to the Honeywell login link despite the fact that (I thought) I was configuring it to login to a different URL. I'm most likely doing something wrong, but is it obvious what that might be? Thank you again for your help! Here is the error output upon trying to call the associated
|
It appears as though one is unable to install the
qiskit-quantinuum-provider
package either via the PyPi server (as it is not present) or via Git. IOW, doing:is broken as the PyPi link is broken. Alternatively, attempting to install the package via Git, that is:
also fails. It seems as if the last commit to this project was at the end of March of 2023. Are there any plans to continue development on this project or has it been deprioritized? If the latter, are there any specific adaptations one would have to do in order to make use of this provider pattern within Qiskit?
fyi @mtreinish, @1ucian0 @chris-theroux
The text was updated successfully, but these errors were encountered: