Developer Notes

Developing Qt for Python requires people to understand different processes and steps that need to be taken into account when dealing with topics related to modules, bindings, examples, and more.

Development Topics

• Add a new module
  • Add bindings
  • Add documentation
• Add a new example or port one
  • Add a new example
  • Port a Qt example
• Add a new tool or a Qt tool wrapper
  • Add a new tool
  • Add a Qt tool wrapper
• Fixing Documentation issues
  • Fixing texts
  • Fixing snippets
  • Maintaining additionaldocs.lst
  • Inheritance graphs
• Test a wheel
• Build on the command line
• De-Virtualize the Python Files

Implementation details

Complementary, here you can find the reasoning and motivation for the many features and implementation details that the project has:

• The Set of Enum Features
  • The Possible Enum Flags
  • The most likely flags needed
  • Flags for completeness
• The Transition To The Limited Python API (PEP384)
  • Foreword
  • Changed Modules
  • Using The New Type API
  • Future Versions Of The Limited API
  • Appendix A: The Transition To Simpler Types
  • Appendix B: Verification Of PyTypeObject
• The signature C extension
  • Short Introduction to the Topic
  • The Idea to Support Signatures
  • Impacts of The Signature Module
  • Literature
• Why do we have a __feature__?
  • History
  • Why are features selectable per-module?
  • Why dunder, and why not __future__?
• The snake_case feature
• The true_property feature
  • Normal Properties
  • Special Properties
  • Class properties
  • About Property Completeness
  • Name Clashes and Solution
• The __feature__ import
  • Overriding __import__
  • IDEs and Modifying Python stub files
  • Using __feature__ with UIC files