[ckan-dev] [RFC] libckan - Python library for APIv3 (Action) and CKAN v2.0.0

[Sean Hammond]

> If you define a Package object in libckan, with a field for each key in
> a CKAN package dict, then every time the fields of a CKAN package change
> in a new version you will have to change that class.

Yeah. Also different CKAN sites can use IDatasetForm to change what
fields their datasets have, you can even have different types of dataset
with different fields on the same site, so it's not stable (there's also
IGroupForm and IOrganizationForm too).

Generally this looks like great work if we can just nudge in a direction
that's gonna be slightly more flexible and less code to maintain in
future, then it looks very promising.