diff options
author | Kavindra Palaraja <kpalaraja@luxoft.com> | 2019-11-19 11:44:41 +0100 |
---|---|---|
committer | Cristián Maureira-Fredes <cristian.maureira-fredes@qt.io> | 2020-01-27 23:40:55 +0100 |
commit | d823a2740d4dabc925f9082f28ac9865188ec8ab (patch) | |
tree | 4eca12a735ecb8442c3c088677403b3f460e02c9 /sources/pyside2/doc/faq.rst | |
parent | edef8f470703a4e8d192f9a2fc154c5cd584fae3 (diff) |
docs: More fixes on deployment and faq
Change-Id: I97d7251b0d9ec024ce069f6475d7bc6be0d9d362
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'sources/pyside2/doc/faq.rst')
-rw-r--r-- | sources/pyside2/doc/faq.rst | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/sources/pyside2/doc/faq.rst b/sources/pyside2/doc/faq.rst new file mode 100644 index 000000000..f1aa3ebcc --- /dev/null +++ b/sources/pyside2/doc/faq.rst @@ -0,0 +1,33 @@ +Frequently Asked Questions +========================== + +**When did The Qt Company adopt PySide2?** + In April 2016 `The Qt Company <https://qt.io>`_ decided to properly support the port. For more + information, see `<https://groups.google.com/forum/#!topic/pyside-dev/pqwzngAGLWE>`_. + +**Why use PySide2 and not PySide?** + Since PySide was developed for Qt 4, we now use PySide2 to imply that it is for a newer version, + after it was ported to support Qt 5. + +**Where I can find information about the old PySide project?** + The project's old wiki page is available on PySide, but the project is now deprecated and not + supported. + +**There are three wheels (pyside2, shiboken2, and shiboken2_generator), what's the difference?** + + Before the official release, everything was in one big wheel, so it made sense to split these + into separate wheels, each for the major projects currently in development: + + * **pyside2**: contains all the PySide2 modules to use the Qt framework; also depends on the + shiboken2 module. + * **shiboken2**: contains the shiboken2 module with helper functions for PySide2. + * **shiboken2_generator**: contains the generator binary that can work with a C++ project and a + typesystem to generate Python bindings. + If you want to generate bindings for a Qt/C++ project, there won't be any linking to the Qt + shared libraries; you need to do this by hand. We recommend building PySide2 from scratch + to have everything properly linked. + +**Why is the shiboken2_generator not installed automatically?** + It's not necessary to install the shiboken2_generator to use PySide2. The package is a result of + the wheel splitting process. To use the generator, it's recommended to build it from scratch to + have the proper Qt linking. |