This implements support for pagination Fix #59

By default list method retrieves all the objects navigating the pages returned by the API all argument allows to disable pagination and return all the results (implementing current behavior) lazy_pagination argument allows to load a single page

I've added a basic configuration to build .deb packages of the module for Debian-based systems.

The configurations is not complete enough to get accepted into the official Debian repository, but it ought to suffice if someone wanted to set up a PPA, for example. Personally, I need the .deb-packaged version to be able to distribute the module in a particularly Debian-centric environment.

Pybuild does the heavy lifting based on your existing setup.py file. A single command, which I've encapsulated in the Makefile, is enough to build the packages for both Python 2 and 3.

If this is merged, the Maintainer field (line 4 in debian/control) should probably be changed to (one of) the repository maintainers from here.

This will add the ability to set existing custom attributes (fixes #18). Adds version to allowed_params in class UserStory and Task (maybe needs in Issue too?) (fixes #17). Forwards **attrs in UserStory add_task (fixes #16 )

Hi,

I think one of the latest taiga-back commits broke python-taiga if not entirely but quite badly. I see they made changes to the history management in taiga-back (they fixed something with timeline history loops on fresh projects) and I suppose it had some effect on this tool.

This gets raised when I'm trying to get a project by its slug: AttributeError: 'History' object has no attribute 'id'

Got no idea where to fix it yet.

Hi @nephilaweb, thanks for the python-taiga api.

This is my first time writing some python scripts and I would love to have some guidance of how to test my changes well.

I extended some models so it's more usable in tools and also added an epic-support.

Can you guide me along the way? I will update this pull request with the changes necessary to get this merged.

Thanks! Cheers

I was using this API to send out a massive amount of invites for a class to create public projects and adding members. It throttled at adding members. For some reason, my connection to Taiga Server is extremely slow. I have 100mbps at home and it takes 5 secs to load the website. I am not sure if it has anything to do with it. Thoughts? Thank you!

Hi,

As an LDAP user, I would like to have an ldap auth provided by python-taiga. I can't use python-taiga as long as ldap auth is not supported.

Thanks in advance.

First of all: wonderful project, I like working with python-taiga!

I want to fetch out some project stats but the stats API calls for Projects and Milestones were missing. I added these two calls and associated test cases with them.

API doc: http://taigaio.github.io/taiga-doc/dist/api.html#projects-stats http://taigaio.github.io/taiga-doc/dist/api.html#milestones-stats

Description

Hi, I want to get project slug. I need project slug to create full front-end link (eg. https://mytaigahost.com/project/<project_slug>/us/<userstory_id>) of user stories and tasks. Sorry, but I don't understand how to get it. Can you help me?

Steps to reproduce

projects = api.projects.list() not return project slug.

Versions

python-taiga 1.0.0 taiga 6.0.0

Hello,

I noticed that if you use python-taiga against https://api.taiga.io/ to list projects it fails.

api.projects.list()
(Traceback (most recent call last):
  File "./taiga-stats", line 175, in cmd_list_projects
    for proj in api.projects.list():
  File "/home/erikw/.virtualenvs/taiga-stats/lib/python3.6/site-packages/taiga/models/base.py", line 41, in list
    objects = self.parse_list(result.json())
  File "/home/erikw/.virtualenvs/taiga-stats/lib/python3.6/site-packages/requests/models.py", line 892, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

No output fed in to the JSON decoding? So I decided to get down to my friend command line, and this works as expected:

$ curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer ${AUTH_TOKEN}" -s https://api.taiga.io/api/v1/projects
...
<project JSON>

So I drilled down the code and noticed that python-taiga always send the header

x-disable-pagination: True

to disable pagination and get everything at once.

So I plugged this in to the the previous command line

$ curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer ${AUTH_TOKEN}" -H "x-disable-pagination: True" -s https://api.taiga.io/api/v1/projects
<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.10.3 (Ubuntu)</center>
</body>
</html>

and now it it also fails like when called with pyhon-taiga.

I simply think this is the situation: now the number of public projects at taiga.io has recently grown too large to be included in one GET request to the project listing API endpoint. But before it was small enough to work.

A user of my project taiga-stats reported this last week.

I guess python-taiga should be adapted to use pagination for requests, so it can handle large taiga instances, like taiga.io now is. And I think this is prioritized to to, as I guess taiga.io is the most used instance of Taiga of them all!

Allow the connection to a Taiga host using a self-signed certificate (also ignore the InsecureWarning triggered by urllib3).

Taiga offers other types of authentication (LDAP, github, ...), so the key 'type' in the payload for the auth request can't be hard coded to 'normal'.

Add Epic Custom Attributes

Description

Describe:

• Content of the pull request
• Feature added / Problem fixed

References

Provide any github issue fixed (as in Fix #XYZ)

Checklist

• [ ] I have read the contribution guide
• [ ] Code lint checked via inv lint
• [ ] changes file included (see docs)
• [ ] Usage documentation added in case of new features
• [ ] Tests added

Add EpicAttribute and EpicAttributes

Description

Describe:

• Content of the pull request
• Feature added / Problem fixed

References

Provide any github issue fixed (as in Fix #XYZ)

Checklist

• [ ] I have read the contribution guide
• [ ] Code lint checked via inv lint
• [ ] changes file included (see docs)
• [ ] Usage documentation added in case of new features
• [ ] Tests added

updates:

• github.com/pre-commit/pre-commit-hooks: v4.0.1 → v4.4.0
• https://github.com/timothycrosley/isort → https://github.com/PyCQA/isort
• github.com/PyCQA/isort: 5.9.3 → 5.11.4
• github.com/psf/black: 21.9b0 → 22.12.0
• https://gitlab.com/pycqa/flake8 → https://github.com/PyCQA/flake8
• github.com/PyCQA/flake8: 3.9.2 → 6.0.0
• github.com/asottile/pyupgrade: v2.29.0 → v3.3.1

Clarify that description is not available in the list responses

References

Fix #105

Checklist

• [x] I have read the contribution guide
• [x] Code lint checked via inv lint
• [x] changes file included (see docs)
• [x] Usage documentation added in case of new features
• [ ] Tests added

Description

Page parameter was not passed to querystring, thus pagination failed

Ensure page parameter is actually passed to query parameters

References

Fix #116

Checklist

• [x] I have read the contribution guide
• [x] Code lint checked via inv lint
• [x] changes file included (see docs)
• [ ] Usage documentation added in case of new features
• [x] Tests added

Description

when you have more than 300 User stories (2071 in the one I'm working with) setting page=y will return the same results no matter the value of y

Steps to reproduce

    the_page_size = 100

    for y in range(1,10):
        stories = api.user_stories.list(project=44, page=y, page_size=the_page_size)
        for x in stories:
            print(x.subject)
        print("*** Page *** ", y, "Len: ",len(stories))

Versions

Expected behaviour

when incrementing "page" and re calling I would expect the next page of results to be returned

Actual behaviour

whatever value is set the first page is returned

Additional information