[Tools-discuss] Re: documents by WG --- RFCs and related documents -- are there APIs

[Robert Sparks <[e-mail]>]

On 7/31/25 11:00 PM, Jay Daley wrote:
> Tom
>
>> On 31 Jul 2025, at 06:18, Tom Pusateri <[e-mail]> wrote:
>>
>> Well, that’s the whole point of a versioned API. When you make model changes, you do so in a way that preserves the old API too. And while you offer a new (v2) API, you never break the old API.
>>
>> It’s just a choice when adding new features. You can choose to break the old API or you can choose to preserve it.
> You make it sound like a zero-cost choice when in practice it can be, and is in our case, a very expensive choice to make.
>
> Jay

The TastyPie API (known as /api/v1/) is something we would not have 
provided in retrospect - it is, as others have pointed out, a very 
simplistic  exposure of the django models and a very limited subset of 
the django queryset mechanisms. When we provide new apis that abstract 
the backend away (and allow us to maintain backwards compatibility when 
the models or even the core infrastructure of the backend changes) we 
MUST deprecate /api/v1. That time will come, but it's not in the 
immediate future.

It would be useful for anyone using the v1 API for applications to let 
us know the core queries they rely on so we can begin to proactively 
provide alternatives that are easier to keep stable.

RJS