-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
README.md - update to highlight "DO **NOT** USE WITH IPYTHON 7" - it WILL corrupt your installation. #22
Comments
I think corrupting is a strong word. If you disable and remove rlipython
IPython has no reasons to be broken.
If you send a pr updating the readme I'd be happy to merge. Updating
setup.py to mark the dependencies as IPython<7 is also a possibility. And
actually updating this repo to work with 7+ would be nice. It's just an
open source project so we usually scratch our own itch on our own free
time. Contributions and help always welcome.
…On Tue, Mar 26, 2019, 19:37 Stephen McGregor ***@***.***> wrote:
A single sentence at the top of the README.md, should be a quick fix
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#22>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUez6efbWnF-EUr4UN_U3WKzPF7mpXRks5vatl6gaJpZM4cM1JN>
.
|
Well, fyi, after trying to remove rlipython, I can't run run ipython
Note: *[TerminalIPythonApp] CRITICAL | Bad config encountered during initialization: You're right, I should edit setup.py and make a PR. |
Yeah I'm having the same problem. Can't get into ipython to uninstall, not even with --simple-prompt. Pip uninstall and reinstall of ipython doesn't fix the issue. Update: Back on track here. I ended up creating a new ipython profile and logging into that to uninstall rlipython. You can also replace contents of .ipython\profile_default\ipython_config.json with {}. |
A single sentence at the top of the README.md, should be a quick fix
The text was updated successfully, but these errors were encountered: