After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755385 - Make the giscanner modules public
Make the giscanner modules public
Status: RESOLVED OBSOLETE
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-09-22 07:04 UTC by Mikhail Zabaluev
Modified: 2018-02-08 12:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mikhail Zabaluev 2015-09-22 07:04:06 UTC 
Currenty the Python modules are considered private to gobject-introspection and installed in a project-specific location. However, while implementing a code generator for my bindings project, I've found most of those modules highly reusable, and the "public" Python API looks fairly stabilized. It's a pity to have to copy the modules in order to ensure stability in my own project, rather than just managing them as any other site-packages dependency.
Comment 1 Cosimo Lupo 2016-02-17 09:40:55 UTC 
+1
Comment 2 Emmanuele Bassi (:ebassi) 2017-05-04 21:19:59 UTC 
The main point against making these modules public is that there is no guarantee whatsoever of API stability, currently, and installing them would make that guarantee.
Comment 3 GNOME Infrastructure Team 2018-02-08 12:37:40 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/142.