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 571834 - Documentation for Python GIO bindings is missing
Documentation for Python GIO bindings is missing
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: gio
unspecified
Other All
: High normal
: ---
Assigned To: Gian Mario Tagliaretti
Python bindings maintainers
: 578067 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-15 14:48 UTC by Vadim Peretokin
Modified: 2009-05-17 14:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Vadim Peretokin 2009-02-15 14:48:46 UTC
Documentation 
Section: pygtk?
It does not mention GIO at all.

Correct version:
It should document GIO.

Other information:
Developers are not happy: http://ubuntuforums.org/showpost.php?p=6738023&postcount=126
Comment 1 Gian Mario Tagliaretti 2009-02-16 21:52:29 UTC
(In reply to comment #0)
> Documentation 
> Section: pygtk?
> It does not mention GIO at all.

Yup documentation for GIO is not yet available (nobody has started writing the docs)

> Correct version:
> It should document GIO.

Ehmmm... yes it should.

> Other information:
> Developers are not happy:
> http://ubuntuforums.org/showpost.php?p=6738023&postcount=126

If developers are not happy, and I can understand that, they should pop in #pygtk and offer some help in writing it.

Please note that it can sound harsh but it's not, that's what I did many years ago when I started contributing to Gnome.
Comment 2 Vadim Peretokin 2009-02-16 21:57:52 UTC
I was following the bug tracker instructions, that's why the text is there.

I'll ask the developer on helping to write it - but I have a feeling he wanted to use the documentation, not write it.
Comment 3 Paul Pogonyshev 2009-02-16 22:02:08 UTC
There is some minimalistic and incomplete documentation in .defs files, but it seems to be unused (except from Python built-in help which probably no-one seriously uses).  Even some auto-generated help with at least lists of functions and these short blurbs (where available) would be an improvement.
Comment 4 Gian Mario Tagliaretti 2009-02-16 22:29:32 UTC
(In reply to comment #2)
> I was following the bug tracker instructions, that's why the text is there.

Of course Vadim, don't get me wrong thanks a lot for your bug report.

> I'll ask the developer on helping to write it - but I have a feeling he wanted
> to use the documentation, not write it.

eheh this is what I meant, everybody wants to _use_ it, but it takes a lot of effort in writing it.
Comment 5 Vadim Peretokin 2009-02-17 00:08:45 UTC
Well, less people want to use it if it's not there. It's not like open-source programs can only benefit from 'everyone' wanting to use it ;)
Comment 6 John Finlay 2009-02-17 00:15:57 UTC
Open Source is a community. It works best when people who see a need (esp. for themselves) willingly pitch in to help satisfy that need.
Comment 7 Vadim Peretokin 2009-02-17 00:38:25 UTC
Sure, and that is why the program is being made to begin with.

But it is a turn off when the tools are of poor quality / lacking.
Comment 8 Gian Mario Tagliaretti 2009-04-05 20:49:44 UTC
*** Bug 578067 has been marked as a duplicate of this bug. ***
Comment 9 Gian Mario Tagliaretti 2009-04-05 20:58:25 UTC
It's a work in progress, I've already wrote the docs for quite some classes, see SVN trunk.
Comment 10 Vadim Peretokin 2009-04-05 21:33:28 UTC
Great, thank you
Comment 11 Gian Mario Tagliaretti 2009-05-17 14:57:17 UTC
Some parts are still missing, we could use some help.
I'm closing as fixed since with or without help we are going to finish it.