Bug 751146
Summary: | Ipython forgets configuration after upgrade, doesn't let me install new one. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nils Philippsen <nphilipp> |
Component: | ipython | Assignee: | Thomas Spura <tomspur> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | mrunge, shahms, tomspur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-13 23:44:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nils Philippsen
2011-11-03 16:39:45 UTC
Thanks for filling this bug. Unfortunately this is kind of expected by upstream... * As I understood upstream, there won't be a migration tool for moving the configuration (This was the main blocker for not shipping as an update in an released version, so users are only hitting this, when upgrading.). * upstream is furthermore working on more documentation for the new configuration and has your "how to configure the prompt" only in the outdated section [1] You might find this usefull: http://ipython.org/ipython-doc/dev/config/ipython.html e.g. adding this to ~/.config/ipython/profile_default/ipython_config.py and you won't have an exit prompt: """ c = get_config() c.InteractiveShell.confirm_exit = False """ Hope this is helpful. [1] http://ipython.org/ipython-doc/dev/config/old.html ############################################################################## In [1]: %install_default_config Installing default config file in: /home/tom/.config/ipython/profile_default So the macro seems to work, but it fails, when you have the old directory, see: https://github.com/ipython/ipython/issues/467 But doesn't seem to be the case in your backtrace. Or what config files do you still have around or new created? I get the above traceback if I move both .ipython and .config/ipython out of the way, then start ipython and execute %install_default_config. BTW, I get my old configuration (resembling the classic interactive python) back with this configuration in .config/ipython/profile_default/ipython_config.py: --- 8< --- c = get_config() c.InteractiveShell.confirm_exit = False c.InteractiveShell.prompt_in1 = ">>> " c.InteractiveShell.prompt_in2 = "... " c.InteractiveShell.separate_in = "" c.InteractiveShell.prompt_out = "" --- >8 --- This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |