Metadata-Version: 2.1
Name: django-popolo
Version: 3.0.2
Summary: A Django-based implementation of the OpenGovernment context, compliant with the Popolo data specifications.
Home-page: http://github.com/openpolis/django-popolo
Author: Guglielmo Celata
Author-email: guglielmo@openpolis.it
License: AGPL-3.0
Description: # django-popolo
        
        Welcome to the documentation for django-popolo!
        
        **django-popolo** is a django-based implementation of the
        [Popolo's open government data specifications](http://popoloproject.com/).
        
        It is developed as a Django reusable app to be deployed directly within Django projects.
        
        It will allow web developers using it to manage and store data according to Popolo's specifications.
        
        The standard sql-oriented Django ORM will be used.
        
        From release 1.2.0, django-popolo includes classes that extend the model, although compatibility
        with the standard is kept.
        
        Release 2.0.0 introduces a change in how Sources and Links are referred to,
        that breaks compatibility with the popit importer.
        
        Release 3.0.0 main focuses have been to keep up with latest Django
        versions and to "modernize" the code base, adopting latest Python features (like type hinting), 
        and doing some serious housekeeping. Python 2 is no longer supported. 
        This release also implements a lot of new models which are not part of the Popolo specification (mildly out of scope), 
        but we needed them in some projects which make use this package. Those new models can be safely ignored, and they could 
        also be removed in the future, as we are considering the option of entirely decoupling them from `django-popolo`. 
        
        
        See the [CHANGELOG.md](./CHANGELOG.md) file for more details.
        
        ## Installation
        
        To install `django-popolo` as a third party app within a django project,
        you need to add it to the django project's requirements.txt.
        You can do this from GitHub in the usual way, or using the
        `django-popolo` package on PyPI.
        
        ## Notes on mysociety's fork
        
        [mysociety/django-popolo](https://github.com/mysociety/django-popolo) is a fork of this project where integer IDs are used
        instead of slugs.
        
        Our packages, since version 1.1 also uses numerical ids as primary keys for all entities.
        Slugs are available as non-primary fields, for the 4 main classes (`Person`, `Organization`, `Post`, `Membership`).
        Slugs are used through the `Permalinkable` behavior, that adds the `slug` field to the class, populating it according to rules defined in each class.
        
        
        
Platform: UNKNOWN
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Framework :: Django
Classifier: Framework :: Django :: 1.11
Classifier: Framework :: Django :: 2.2
Classifier: License :: OSI Approved :: GNU Affero General Public License v3
Classifier: Development Status :: 4 - Beta
Classifier: Operating System :: OS Independent
Description-Content-Type: text/markdown
Provides-Extra: test
Provides-Extra: dev
