Goal here is to create a brand new API in pyteamcity.future that is much more flexible and to have nicer code that is easier to work with. The old code encourages adding a zillion methods for different ways of filtering. The new code has an API with a smaller number of methods that are more consistent and more flexible in terms of filtering. It is modeled loosely after the Django ORM API.
The plan is to make this available as pyteamcity.future for a few releases while still retaining the old legacy API as pyteamcity, so existing code using that API still works. Then after a few releases, I would remove the legacy API and rename pyteamcity.future to pyteamcity and it would be the only supported API.
Goal here is to create a brand new API in
pyteamcity.future
that is much more flexible and to have nicer code that is easier to work with. The old code encourages adding a zillion methods for different ways of filtering. The new code has an API with a smaller number of methods that are more consistent and more flexible in terms of filtering. It is modeled loosely after the Django ORM API.The plan is to make this available as
pyteamcity.future
for a few releases while still retaining the old legacy API aspyteamcity
, so existing code using that API still works. Then after a few releases, I would remove the legacy API and renamepyteamcity.future
topyteamcity
and it would be the only supported API.