[Bug 1005452] New: Outdated information

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1005452

            Bug ID: 1005452
           Summary: Outdated information
           Product: Fedora Documentation
           Version: devel
         Component: rpm-guide
          Severity: medium
          Assignee: bcotton+fedora at gmail.com
          Reporter: cickumqt at gmail.com
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: bcotton+fedora at gmail.com, pkovar at redhat.com,
                    zach at oglesby.co



Quoted from
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s07.html:

The RPM bindings for Python are documented along with the C programming API. On
a Red Hat Linux system, look in the file
/usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html to see the start
of the Python-specific documentation.
Note that much of this online documentation covers the C functions that provide
the Python bindings, not the Python API itself. But, if you examine the online
information on objects listed as classes, such as rpmts, you can find the
Python-specific documentation.
Furthermore, if you look into the .c files that make up the Python bindings,
you can find PyMethodDef structure tables. These tables provide useful glimpses
into the Python API.
To learn more about programming in Python, install the python-docs package. The
python-docs package has a large set of online documentation for Python,
including the official Python Tutorial. With Red Hat Linux, start at
/usr/share/doc/python-docs-2.2.1/html/tut/tut.html.
Cross Reference
Other tutorials are available at http://diveintopython.org for the Dive Into
Python tutorial for experienced programmers, and at
http://py.vaults.ca/parnassus/apyllo.py/935043691.636055170 for the Vaults of
Parnassus listing of tutorials.


I think we need to update some words like RPM4.1,
/usr/share/doc/python-docs-2.2.1 (F20 docdir changes) and Red Hat Linux ....

-- 
You are receiving this mail because:
You are the QA Contact for the bug.