Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 6a44c51

Browse filesBrowse files
committed
Update docs re: pygobject in venv.
PyGObject can now be built in a venv, added link to their instructions. Reworded an awkward sentence.
1 parent 6af4e4f commit 6a44c51
Copy full SHA for 6a44c51

File tree

Expand file treeCollapse file tree

1 file changed

+9
-5
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+9
-5
lines changed

‎doc/faq/virtualenv_faq.rst

Copy file name to clipboardExpand all lines: doc/faq/virtualenv_faq.rst
+9-5Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,19 +28,23 @@ PyQt5 yes yes
2828
------------- -------------------------- ---------------------------------
2929
PyQt4 PySide: on Windows and OSX yes
3030
------------- -------------------------- ---------------------------------
31-
PyGObject no on Linux
31+
PyGObject yes [#]_ on Linux
3232
------------- -------------------------- ---------------------------------
3333
wxPython yes [#]_ yes
3434
============= ========================== =================================
3535

36+
.. [#] No wheels available, see
37+
https://pygobject.readthedocs.io/en/latest/devguide/dev_environ.html
38+
for build instructions.
39+
3640
.. [#] OSX and Windows wheels available on PyPI. Linux wheels available but
3741
not on PyPI, see https://wxpython.org/pages/downloads/.
3842
3943
For cases where the framework is not installable in a venv, it needs to be
40-
install the package in the global (system) site-packages, and then made
41-
available from within the venv. This can be achieved by either of the
42-
following methods (in all cases, the system-wide Python and the venv Python
43-
must be of the same version):
44+
installed in the global (system) site-packages, and then made available from
45+
within the venv. This can be achieved by either of the following methods (in
46+
all cases, the system-wide Python and the venv Python must be of the same
47+
version):
4448

4549
- `vext <https://pypi.python.org/pypi/vext>`_ allows controlled access
4650
from within the virtualenv to specific system-wide packages without the

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.