PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 135 - Support versioning attributes in tags to manage different API versions
: Support versioning attributes in tags to manage different API versions
Status: CLOSED FIXED
Product: PySide
Classification: Unclassified
Component: ApiExtractor
: HEAD
: All All
: P5 enhancement
Assigned To: renato filho
:
:
:
  Show dependency treegraph
 
Reported: 2010-01-22 11:43 EET by Lauro Moura
Modified: 2010-06-10 10:47 EEST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lauro Moura 2010-01-22 11:43:32 EET
Currently boost-based PySide bidings uses multiple typesystem files to handle
different Qt versions. For examples, there is a *_40.xml for the API up to 4.5
and 4.6 stuff loads the 4.5 typesystem from its own _46.xml file. This ends up
with .in file that are processed with CMake.

The proposed solution is adding two attributes for new stuff and deprecated
stuff, making the typesystem able describe always the newest version.

New things would have an attribute 'since=VERSION', stating the since the given
version this object/method/modification is available and should be included.

Deprecated things will have an attribute 'deprecated=VERSION'. So if the
current version is greater or *equal* to VERSION, the
object/method/modification will be marked as deprecated *and* not included by
default. Although it would be useful to have a command line option or flag to
make them available with some special attribute, if someone wishes to include
deprecated function with a deprecation warning.
Comment 1 renato filho 2010-06-10 10:47:26 EEST
fixed on last release 0.3.2.