Python interface to Request Tracker API

Edit Package python-rt
https://github.com/CZ-NIC/python-rt

Python implementation of Request Tracker (a ticketing system) REST API described here: https://rt-wiki.bestpractical.com/wiki/REST

Refresh
Refresh
Source Files
Filename Size Changed
python-rt.changes 0000006092 5.95 KB
python-rt.spec 0000001734 1.69 KB
rt-3.0.0.tar.gz 0000065949 64.4 KB
Revision 23 (latest revision is 42)
Sebastian Wagner's avatar Sebastian Wagner (sebix) committed (revision 23)
- update to version 3.0.0
 - The following is a major release of the `rt` library.
  - There is support for the REST API version 1 as well as version 2.
  - Please note that this release contains breaking changes and requires adaptations to existing code, even if you are sticking to version 1 of the API.
  - These changes were necessary in order to properly support both API versions.
 - Added
  - RT REST2 support was added and is mostly on par with the REST1 support (differences are a result of the REST2 API implementation differences in RT).
  - REST2 is a modern API based on JSON exchanges and thus the complex parsing of responses and request construction are no longer needed.
 - Changes
  - Existing exception classes were renamed to adhere to the naming convention (https://peps.python.org/pep-0008/#exception-names).
   - In case you do catch specific `rt` exceptions, a simple search/replace will do, see the changelog page in the documentation for details.
  - Importing the `rt` class changed in order to better accommodate the new `rest2` implementation.
   - Where one use to be able to import `rt` using:
     `from rt import Rt`
     you now have to use the following syntax:
     `from rt.rest1 import Rt`
  - Importing the `rt` module does no longer import all exceptions but only the core `RtError` exception.
  - If you require other exceptions, please import them from `rt.exceptions`.
  - Use pytest instead of nose.
Comments 1

Duarte Pousa's avatar

Hello,

The latest revision as of today (rev 29) is not functional, even though the build is successful, it results in the following:

rpm -ql python310-rt
/usr/lib/python3.10/site-packages/UNKNOWN-0.0.0-py3.10.egg-info
/usr/lib/python3.10/site-packages/UNKNOWN-0.0.0-py3.10.egg-info/PKG-INFO
/usr/lib/python3.10/site-packages/UNKNOWN-0.0.0-py3.10.egg-info/SOURCES.txt
/usr/lib/python3.10/site-packages/UNKNOWN-0.0.0-py3.10.egg-info/dependency_links.txt
/usr/lib/python3.10/site-packages/UNKNOWN-0.0.0-py3.10.egg-info/top_level.txt
/usr/share/doc/packages/python310-rt
/usr/share/doc/packages/python310-rt/AUTHORS
/usr/share/doc/packages/python310-rt/CHANGELOG.md
/usr/share/doc/packages/python310-rt/README.rst
/usr/share/licenses/python310-rt
/usr/share/licenses/python310-rt/LICENSE

Looking at the changelog, it may be related to this change from upstream:

- Move package metadata and configuration from setup.cfg to pyproject.toml.
openSUSE Build Service is sponsored by