Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-04-09 | fix: use `python3` for all `python` invocations (#10832) | Carlo Sala | |
2021-12-31 | chore(python): minor corrections on README (#10548) | vladislav doster | |
Closes #10548 | |||
2021-12-29 | feat(python): add utilities to manage simple virtual environments (#9776) | Marijan Smetko | |
Closes #9776 | |||
2021-12-29 | feat(python): add `pyserver` alias to start an HTTP server (#10217) | Celestino Gomes | |
Closes #10217 | |||
2021-10-04 | docs(python): update README to include new `py` alias (#9995) | Dani Torramilans | |
2020-03-02 | python: add pyuserpaths function (#7758) | 0b10 | |
Summary Make it get a list of installed interpreters, and add the relevant local (HOME) site-packages directory to PYTHONPATH. Reason To easily add all relevant paths, initially, and between upgrades. Add check for PYTHONUSERBASE Summary Check for a non-standard install directory, use it if one exists, otherwise use ~/.local. Reason Allow users to specify their own installation directory, without affecting functionality. | |||
2020-02-27 | python: add alias to run the proper IPython based on virtualenv | Petr Bělohlávek | |
Current state: a user invokes `ipython` and is provided with the IPython instance regarding the `$PATH`. Proposed state: a user invokes `ipython` (which is a new alias in the *python plugin*) and is provided with the proper IPython instance regarding the currently activated virtualenv. Example: the user's default Python is 2.7 with installed IPython 2.7. User activates Python 3.5 virtualenv where he installs IPython 3.5. After activating the environment, one expects `ipython` to run the version 3.5, which does not happen by default. Instead, IPython 2.7 is used, which in counter-intuitive and often causes problem. Closes #5797 | |||
2018-10-02 | python: add README (#7191) | Sagar Patil | |