4.0.0

What's Changed

• Update PredictHQ logo and minor text changes by @robertkern in #94
• Se 1513 implement retry by @medhatphq in #95

Full Changelog: 3.6.0...4.0.0

3.6.0

SE-1622 Updated Event schema to include geo.address and start_local, end_local and predicted_end_local fields.

Full Changelog: 3.5.0...3.6.0

3.5.0

What's Changed

• SE-1356 Modify features endpoint to dynamically set requested features. by @medhatphq in #92

Full Changelog: 3.4.0...3.5.0

3.4.0

What's Changed

• make CountResultSet top_rank optional for the case where count is 0 by @corke2013 in #91

Full Changelog: 3.3.0...3.4.0

3.3.0

What's Changed

• fix accept decorator bug by @corke2013 in #90

Full Changelog: 3.2.0...3.3.0

3.2.0

What's Changed

• Update SDK to surface PHQ_LABELS by @corke2013 in #89

Full Changelog: 3.1.0...3.2.0

3.1.0

What's Changed

• add new features for DIP accommodation, and hospitality as well as phq_spend by @CockyAmoeba in #88

Full Changelog: 3.0.0...3.1.0

3.0.0

Version 3.0.0 adds support for python3.10+.

In order to do so, we had to drop support for python3.6 and replace our internal usage of the schematics library by Pydantic.

This came with a few changes that we listed down below.
If you notice any issues using this new version, please create an issue so that we can fix is asap.

V3 breaking changes details

V3 introduces support for Python versions above 3.9 and drops support for Python3.6.

In order to allow the following, we replaced the Schematics package (which is not maintained anymore and incompatible with python3.10+) by Pydantic.

We used to perform data validation on query params before sending the request to our API. This has been dropped in order to let our API validate query parameters as it's meant to.

The above induced a few breaking changes from prior versions. If you are migrating from version 2.4.0 or below to version 3.0.0 or above, please, take the time to read the following.

No more support for Python3.6

As stated above, from version 3.0.0 onward, our SDK won't be available for python version below 3.7.

Fetched objects methods changed

The SDK endpoints used to return Schematics objects. They now return Pydantic objects.

Here follows a list of functions that won't be accessible on returned objects anymore and their pydantic equivalent:

Schematics Method Name	Pydantic Equivalent
obj.flatten()	❌
obj.items()	list(obj.model_dump().items())
obj.iter()	obj.model_dump().items()
obj.keys()	obj.model_fields_set() or list(obj.model_fields_set()) if you need it to be a list of strings
obj.serialize()	obj.model_dump() or json.loads(obj.model_dump_json()) if you wish to have dates as strings and not datetimes
obj.to_dict()	obj.model_dump()
obj.to_native()	❌
obj.to_primitive()	❌ (behaves the same as model_dump)
obj.values()	list(dict(obj).values())

For more Pydantic objects available methods, please check out Pydantic Documentation.

Note: Pydantic will serialize all fields present on the models. If you wish to exclude None fields or fields that were missing from the API responses, use the exclude_none=True or exclude_unset=True function parameters when using the model_dump and model_json_dump functions.

Please do not hesitate to lodge an issue if any valuable behaviour that you were using through schematics objects are not achievable through pydantic objects.

Event Search within parameter

When using the within query parameter for searching events, we used to allow multiple ways of providing the data for this filter:

phq.events.search(within="[email protected],174.768368")
phq.events.search(within={"radius": "2km", "longitude": -71.0432, "latitude": 42.346})
phq.events.search(within__radius="2km", within__longitude=-71.0432, within__latitude=42.346)

Since we are not loading the query params data into objects and not validating it anymore, only the first example will be available from now on (which is the format described in our documentation)

So if you were using the within filter sequentially, using __ or with a dictionary, you will need to update it as follows

phq.events.search(within="[email protected],174.768368")

Exception update

Previously, if you would provide an incorect parameter to an endpoint, the method would raise a predicthq.exceptions.ValidationError.

This error would be formatted as follows

predicthq.exceptions.ValidationError: {'<field_name>': '<reason>'}

Since we are not performing validation within the SDK, the raised exception will instead contain the error message provided by our API.

The exception type has also been changed from predicthq.exceptions.ValidationError to predicthq.exceptions.ClientError.

Those errors will be formatted as follows

{'error': '<API Error description>', 'code': 400}

Cannot use classes as query parameters anymore

Our endpoints used to allow users to use a schematics instance as a query parameter when querying our APIs.

e.g.

from predicthq import Client
from predicthq.endpoints.v1.events.schemas import SearchParams

phq = Client(access_token="abc123")

query_params = SearchParams().import_data({
    "q": "Katy Perry",
    "state": ["active"],
    "rank_level": [4, 5],
    "category": "concerts"
})

for event in phq.events.search(query_params):
    print(event.rank, event.category, event.title, event.start.strftime("%Y-%m-%d"))

This feature was undocumented, so we are not expecting many or anyone to have used it ever.

In the unlikely event that you were using those, you will need to update it as one of the following as this is not supported anymore

from predicthq import Client
from predicthq.endpoints.v1.events.schemas import SearchParams

phq = Client(access_token="abc123")

query_params = {
    "q": "Katy Perry",
    "state": ["active"],
    "rank_level": [4, 5],
    "category": "concerts"
}

# Either

for event in phq.events.search(**query_params):
    print(event.rank, event.category, event.title, event.start.strftime("%Y-%m-%d"))

# OR

for event in phq.events.search(q="Katy Perry", state=["active"], rank_level=[4, 5], category="concerts"):
    print(event.rank, event.category, event.title, event.start.strftime("%Y-%m-%d"))

Beta fixes

Minor fixes: Updated models to account for more optional fields.

Support for Python3.10+

V3 breaking changes details

V3 introduces support for Python versions above 3.9 and drops support for Python3.6.

In order to allow the following, we replaced the Schematics package (which is not maintained anymore and incompatible with python3.10+) by Pydantic.

We used to perform data validation on query params before sending the request to our API. This has been dropped in order to let our API validate query parameters as it's meant to.

The above induced a few breaking changes from prior versions. If you are migrating from version 2.4.0 or below to version 3.0.0 or above, please, take the time to read the following.

No more support for Python3.6

As stated above, from version 3.0.0 onward, our SDK won't be available for python version below 3.7.

Fetched objects methods changed

The SDK endpoints used to return Schematics objects. They now return Pydantic objects.

Here follows a list of functions that won't be accessible on returned objects anymore and their pydantic equivalent:

Schematics Method Name	Pydantic Equivalent
obj.flatten()	❌
obj.items()	list(obj.model_dump().items())
obj.iter()	obj.model_dump().items()
obj.keys()	obj.model_fields_set() or list(obj.model_fields_set()) if you need it to be a list of strings
obj.serialize()	obj.model_dump() or json.loads(obj.model_dump_json()) if you wish to have dates as strings and not datetimes
obj.to_dict()	obj.model_dump()
obj.to_native()	❌
obj.to_primitive()	❌ (behaves the same as model_dump)
obj.values()	list(dict(obj).values())

For more Pydantic objects available methods, please check out Pydantic Documentation.

Please do not hesitate to lodge an issue if any valuable behaviour that you were using through schematics objects are not achievable through pydantic objects.

Event Search within parameter

When using the within query parameter for searching events, we used to allow multiple ways of providing the data for this filter:

phq.events.search(within="[email protected],174.768368")
phq.events.search(within={"radius": "2km", "longitude": -71.0432, "latitude": 42.346})
phq.events.search(within__radius="2km", within__longitude=-71.0432, within__latitude=42.346)

Since we are not loading the query params data into objects and not validating it anymore, only the first example will be available from now on (which is the format described in our documentation)

So if you were using the within filter sequentially, using __ or with a dictionary, you will need to update it as follows

phq.events.search(within="[email protected],174.768368")

Exception update

Previously, if you would provide an incorect parameter to an endpoint, the method would raise a predicthq.exceptions.ValidationError.

This error would be formatted as follows

predicthq.exceptions.ValidationError: {'<field_name>': '<reason>'}

Since we are not performing validation within the SDK, the raised exception will instead contain the error message provided by our API.

The exception type has also been changed from predicthq.exceptions.ValidationError to predicthq.exceptions.ClientError.

Those errors will be formatted as follows

{'error': '<API Error description>', 'code': 400}

Cannot use classes as query parameters anymore

Our endpoints used to allow users to use a schematics instance as a query parameter when querying our APIs.

e.g.

from predicthq import Client
from predicthq.endpoints.v1.events.schemas import SearchParams

phq = Client(access_token="abc123")

query_params = SearchParams().import_data({
    "q": "Katy Perry",
    "state": ["active"],
    "rank_level": [4, 5],
    "category": "concerts"
})

for event in phq.events.search(query_params):
    print(event.rank, event.category, event.title, event.start.strftime("%Y-%m-%d"))

This feature was undocumented, so we are not expecting many or anyone to have used it ever.

In the unlikely event that you were using those, you will need to update it as one of the following as this is not supported anymore

from predicthq import Client
from predicthq.endpoints.v1.events.schemas import SearchParams

phq = Client(access_token="abc123")

query_params = {
    "q": "Katy Perry",
    "state": ["active"],
    "rank_level": [4, 5],
    "category": "concerts"
}

# Either

for event in phq.events.search(**query_params):
    print(event.rank, event.category, event.title, event.start.strftime("%Y-%m-%d"))

# OR

for event in phq.events.search(q="Katy Perry", state=["active"], rank_level=[4, 5], category="concerts"):
    print(event.rank, event.category, event.title, event.start.strftime("%Y-%m-%d"))