semvec/pypi-packages huggingface dataset:
metaconfig 0.1.4
A ConfigParser bootstraping library
License: BSD

Metaconfig
==========

Metaconfig is a library for centralising your Python's ConfigParser
files.  It is inspired by the logging module where it is increadibly
easy to start writing code that depends on logging whilst deferring
how log messages will be handled until later.

To get started with metaconfig just do::

  import metaconfig
  conf = metaconfig.get_config(__name__)

conf will be a ConfigParser instance.  You can create a centralised
config file to configure multiple applications and libraries.

Further documentation is available at http://packages.python.org/metaconfig/.
widgy-blog 0.1.0
Reusable blog app for Django-Widgy
License: BSD

Django Widgy Blog
=================

This is reusable blog app designed for use with django-widgy_. It can
be utilized as a drop-in addition to a widgy project for creating a
quick, run-of-the-mill blog or as an abstract guide to building your
own custom app that takes advantage of all the wonderful features that
widgy offers.

Quickstart
----------

(This guide assumes that your project is already using widgy. Please see
this tutorial_ if this is not the case.)

1.  Install the package

        $ pip install django-widgy-blog

2.  Add ``widgy_blog`` to your ``INSTALLED_APPS``.

3.  Run ``python manage.py syncdb`` and ``python manage.py migrate`` in
    order to generate the relevant models in the database.

4.  Configure the urls:

    a.  If you're using widgy's ``contrib.urlconf_include`` package, you can
        opt to use widgy_blog as a plugin. This allows admin users of the site
        to take advantage of plugin-specific features, such as editing the url
        route of the blog and customizing its addition to menus. See
        urlconf_include_ for more information.

    b.  Alternatively, you can include the widgy_blog urls within your urls.py
        file as you normally would. Just remember to add them before the
        included Mezzanine urls if your editing the root conf!

5.  That's it. Log in to the admin center and start adding blog posts!

.. _django-widgy: https://github.com/fusionbox/django-widgy
.. _tutorial: http://docs.wid.gy/en/latest/tutorials/widgy-mezzanine-tutorial.html
.. _urlconf_include: http://docs.wid.gy/en/latest/tutorials/widgy-mezzanine-tutorial.html#urlconf-include


CHANGES
=======

0.1.0 (release September 16, 2014)
----------------------------------

- Add model attributes to AbstractBlogLayout and BlogAdmin
  that make them easier to subclass. Update AbstractBlogLayout
  published queryset function to use fewer queries [Scott Clark, #18]
- **Backwards Incompatible:** Registered the ``BlogLayout`` model with widgy.
  If you weren't using this as your Blog layout, you will need to unregister
  it::

      import widgy
      from widgy_blog.models import BlogLayout

      widgy.unregister(BlogLayout)

  If you were already registering the ``BlogLayout`` yourself, you can just
  remove that code.
dj-geocoding 0.2.1
Django integration for geocoding (using Geocodio)
License: BSD
Keywords: dj-geocoding

============
dj-geocoding
============

.. image:: https://travis-ci.org/bennylope/dj-geocoding.svg?branch=master
    :target: https://travis-ci.org/bennylope/dj-geocoding

Django features for simple geocoding. Current support for the Geocodio geocoding service

Read the full docs on `Read the Docs <http://dj-geocoding.readthedocs.org/en/latest/>`_.

Installing
==========

Install dj-geocoding::

    pip install dj-geocoding

Then use it in a project::

    import dj-geocoding

Add your geocoding service API credentials to your `settings.py` file::

    GEOCODIO_API_KEY="SOMEAPIKEY"

Model
=====

Use the optional model mixin to your model if you aren't using PostGIS::

    from dj_geocoding.models import GeoBase

    class MyModel(GeoBase, models.Model):
        pass

This adds the followng fields::

    latitude = models.DecimalField(decimal_places=15, max_digits=18, null=True,
            blank=True)
    longitude = models.DecimalField(decimal_places=15, max_digits=18, null=True,
            blank=True)

Adds a geocode method::

    def geocode(self, \*args, \**kwargs):
        return geocode()

You should extend this in your model, providing the field(s) from which the
address will be pulled::

    def geocode(self):
        return super(MyModel, self).geocode('address')

You can choose the separator for providing a single address, too::

    def geocode(self):
        return super(MyModel, self).geocode('street_address', 'city', 'state',
                seperator=", ")

And additional property attributes for the `point` attribute.

Bulk geocoding
==============

The `bulk_geocode` function takes a queryset and geocodes its member objects.

.. note::

    The model *must* implement a point-type field that behaves like a
    Point field.

Example::

    geocoded_qs = bulk_geocode(MyModel.objects.all())

Specifying the field name::

    geocoded_qs = bulk_geocode(MyModel.objects.all(), field='point')

Manager
-------

The manager class implements a subclassed `QuerySet` with a `geocode` method::

    MyModel.objects.all().geocode()

This returns a queryset of the objects updated (or not) that fit within the
limits of the geocoding service. It is a convenient interface tot he
`bulk_geocode` function.

Admin site
==========

The `GeocodedFilter` filter can be used to filter locations in the admin based
on whether they have been geolocated or not.

The `GeolocateMixin` class can be added to your `ModelAdmin` definition to add
the `geocode_address` admin action. This adds the "geocode address" action to
the admin actions dropdown menu and then will allow you to geocode an entire
queryset from the admin.




History
-------

0.2.1 (2014-12-02)
++++++++++++++++++

* Removes reliance on queryset `geocode` method in admin action
* Adds docs

0.2.0 (2014-09-08)
++++++++++++++++++

* Revise `has_geolocation` method, remove property status
* Added list filter class `GeocodedFilter`

0.1.1 (2014-08-26)
++++++++++++++++++

* Bug fix for handling single None value in _set_point

0.1.0 (2014-08-26)
++++++++++++++++++

* First release on PyPI.