Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 31aeec2

Browse files
committed
Add link to virtualenv docs and an alternative workaround
1 parent db09e7a commit 31aeec2

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

doc/faq/virtualenv_faq.rst

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,9 @@ Working with Matplotlib in Virtual environments
1313
Introduction
1414
============
1515

16-
When running :mod:`matplotlib` in a virtual environment you may discover a
17-
few issues. :mod:`matplotlib` itself has no issue with virtual environments.
16+
When running :mod:`matplotlib` in a
17+
`virtual environment <https://virtualenv.pypa.io/en/latest/>`_ you may discover
18+
a few issues. :mod:`matplotlib` itself has no issue with virtual environments.
1819
However, the GUI frameworks that :mod:`matplotlib` uses for interactive
1920
figures have some issues with virtual environments. Everything below assumes
2021
some familiarity with the Matplotlib backends as found in :ref:`What is a
@@ -106,3 +107,7 @@ framework build within the virtualenv. To run a script you can do
106107
``frameworkpython test.py`` where ``test.py`` is a script that requires a
107108
framework build. To run an interactive ``IPython`` session with the framework
108109
build within the virtual environment you can do ``frameworkpython -m IPython``
110+
111+
In addition
112+
`virtualenv-pythonw-osx <https://github.com/gldnspud/virtualenv-pythonw-osx>`_
113+
provides an alternative workaround which may be used to solve the issue.

0 commit comments

Comments
 (0)