-
Notifications
You must be signed in to change notification settings - Fork 9
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
pinned pydata-sphinx-theme #50
Comments
the issue has been closed so we can now remove the pinned version. also we can remove it from here: https://github.com/search?q=repo%3Aploomber%2Fjupysql%20pydata-sphinx-theme&type=code |
@tl3119 - any progress on this one? |
For this one, is that we need to remove the pinned version, that is remove |
only from environment.yml , then open a PR and we'll see if the tests pass |
also we need to check if we pinned it in other repos: ploomber-engine, pkgmt, sklearn-evaluation, ploomber-core |
Sure, I will do that now |
Pinned in sklearn-evaluation repo. Didn't pinned in other repos. I have opened a PR for sklearn-evaluation repo |
can you share a list of where is it pinned and where is it not? looks like at least jupysql https://github.com/ploomber/jupysql/blob/b0c30bf1020a73c0a30d9362c598d99d7ac5a0fe/doc/environment.yml#L30 and sklearn-evaluation are pinned |
Sure! |
I have submitted the PR for this issue: ploomber/jupysql#573 |
The issue has been addressed now |
we still have a few pending ones right? I just closed jupysql but I think there are others that are pending. |
Yeah, jupysql-interactive-connection is also pinned, I can not fork for this repo. This repo says fork is disabled. |
you can ignore jupysql-interactive-connection, we moved the code to jupysql-plugin so looks like we can close this right? since the only ones that have pinned are jupysql, sklearn-eval and jupysql-interactive-connection jupysql has been fixed |
Yes! |
we had to pin pydata-sphinx-theme due to this: pydata/pydata-sphinx-theme#1274 in this repository and will possibly need to do it in other repos, so once a fix is in place, we should ensure we remove the pinned version
The text was updated successfully, but these errors were encountered: