Pupa

Latest version: v0.11.0

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

0.8.0

Backwards-incompatible changes:

* role no longer defaults to 'member' and is now optional in Person constructor
when used w/ primary_org. if primary_org alone is unambiguous scrapers
can set primary org alone and role will be set automatically
* in accordance w/ OCDEP101, Event.start_time/end_time are now
Event.start_date/end_date

Improvements:

* allow extras to be set on bill actions & event agenda items
* bill actions can now specify times
* add classification field to event agenda items
* resolving organizations checks other names like we do for people

0.7.0

Backwards-incompatible changes:

* moves from split dependency of opencivicdata-divisions/opencivicdata-django
to new unified opencivicdata which also splits into two Django apps
(see python-opencivicdata release notes for more detail)

Improvements:

* allow Memberships to have unresolved `person_name` similar to how other
name resolutions work
* allow linking of VoteEvent to BillAction by setting a matching chamber,
date, and bill\_action
* add Scraper.latest\_session convienience method
* optionally allow setting \_scraped\_name on legislative\_session, which will
be used in session\_list checking if present
* add concept of Pupa identifiers, to aid in resolution

Fixes:

* pupa dbinit --reset now correctly drops dependent pupa tables and migrations
* exit gracefully if the first scrape fails instead of complaining about RunPlan
DB constraint
* complex psuedo-ids are now deterministic (by sorting dict keys)

0.6.0

Backwards-incompatible changes:

* Identify sessions by their identifiers instead of their names (update your `get_session_list()` methods)

Improvements:

* Check for the presence of a `get_session_list()` method instead of `check_sessions = True`
* Resolve an event's participants and its agenda items' related entities 206, 207
* Accept an organization name in `Person.add_membership` for the second parameter 233
* Accept `datetime` dates wherever string dates are accepted 218
* Improve error reporting 214, 230, 231
* Compatible with Django 1.10

Fixes:

* Allow people to hold multiple posts in an organization 244, 247
* Add a `primary_org_name` parameter to `Person.add_term`, to disambiguate organizations with the same classification 223
* Update an object if the explicit order of its related objects has changed 242
* Touch an object's `updated_at` whenever its related objects are updated 226
* Correctly resolve a new person with the same name 232
* Don't raise a resolution error due to multiple matches in cases where zero matches are acceptable

0.5.2

* show run logs in the admin
* start tracking failed runs

0.5.1

* use other\_names for psuedo\_id resolution on people
* fix for postgis:// on Heroku
* remove dump command that required imago
* require py-ocd-django 0.8.0 models

0.5.0

* fix major bug causing deadlock on party import
* fix major bug where legislative\_session changes would wipe the database
* update from Django 1.7 to Django 1.9
* now uses Django's ArrayField, JSONField, etc. instead of external deps
* also now requires Postgres 9.4
* changes to be consistent with Popolo in naming of legislative\_session and vote\_event
* some speedups on import by changing how we use bulk\_create
* experimental Kafka support
* actually use other\_names for person import
* allow delayed resolution of people
* respect locked\_fields during import
* renamed make\_psuedo\_id() to discourage use
* lots of other bugfixes

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.