-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Updating notebook pip install
s after v0.11 release
#4102
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
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
…v011_notebooks_update
When we push the docs, do we have a notion of "stable release" vs "latest dev version" (for the docs)? It would be nice if the first thing users navigating the docs land on is the non |
There is no such notion per se, so the best I could come up with was to rely on manually marking these notebooks (hence the pre-release notice in the notebooks guide). Additional to the notice, we could add the "experimental" tag to the menupoints and mark "dev version" notebooks as such. This would put a little beaker icon next to the menupoint like here: |
thanks for the explanation
…On Wed, May 12, 2021 at 12:10 PM Balint Pato ***@***.***> wrote:
When we push the docs, do we have a notion of "stable release" vs "latest
dev version" (for the docs)? It would be nice if the first thing users
navigating the docs land on is the non --pre notebooks [that may not be
up-to-date with HEAD]
There is no such notion per se, so the best I could come up with was to
rely on manually marking these notebooks (hence the pre-release notice in
the notebooks guide
<https://github.com/quantumlib/Cirq/blob/master/docs/dev/notebooks.md#pre-release-notebooks>
).
Additional to the notice, we could add the "experimental" tag to the
menupoints and mark "dev version" notebooks as such. This would put a
little beaker icon next to the menupoint like here:
[image: image]
<https://user-images.githubusercontent.com/635073/118031078-f96b1c00-b31a-11eb-8b44-ebf624ffc058.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4102 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF4VEYOFMEOYI4LP7LNDE3TNLHCDANCNFSM44XAOBMA>
.
|
Updating notebook `pip install`s after v0.11 release. - Changed all `pip install cirq --pre` to `pip install cirq`. - Removed pre-release notices. - Removed pre-release skip list from isolated_notebook_tests.py. - cirq[contrib] is now cirq-core[contrib] so I updated notebooks and docs - educators/chemistry.ipynb testing is skipped currently until we upgrade OpenFermion to the new Cirq (it is still using `cirq.TrialResult`, that was removed in v0.11)
Updating notebook `pip install`s after v0.11 release. - Changed all `pip install cirq --pre` to `pip install cirq`. - Removed pre-release notices. - Removed pre-release skip list from isolated_notebook_tests.py. - cirq[contrib] is now cirq-core[contrib] so I updated notebooks and docs - educators/chemistry.ipynb testing is skipped currently until we upgrade OpenFermion to the new Cirq (it is still using `cirq.TrialResult`, that was removed in v0.11)
Updating notebook
pip install
s after v0.11 release.pip install cirq --pre
topip install cirq
.cirq.TrialResult
, that was removed in v0.11)