semvec/pypi-packages huggingface dataset:
cmsplugin-team 0.2.0
Django CMS plugin to list team members/employees.
License: BSD

=====================
Django CMS team plugin
=====================

Django CMS plugin to list team members/employees.

Installation
------------

1. Install with pip::

    pip install cmsplugin-team

2. Add `filer` and `cmsplugin_team` to your INSTALLED_APPS in `settings.py`::

    INSTALLED_APPS = (
        ...
        # Imperavi (or tinymce) rich text editor is optional
        'imperavi',
        'filer',
        'cmsplugin_team',
    )

3. Install and configure your preferred rich text widget (optional).

Known to work are `django-imperavi`_ as well as for `django-tinymce`_. Be sure to follow installation instructions for respective editors.

For `django-imperavi`_::

    # install
    pip install django-imperavi

    # settings.py
    INSTALLED_APPS = (
        ...
        'imperavi',
    )

    # urls.py
    url(r'^imperavi/', include('imperavi.urls')),


For `django-tinymce`_::

    # install
    pip install django-tinymce

    # settings.py
    INSTALLED_APPS = (
        ...
        'tinymce',
    )

    # urls.py
    url(r'^tinymce/', include('tinymce.urls')),

.. _django-imperavi: https://github.com/vasyabigi/django-imperavi
.. _django-tinycme: https://github.com/aljosa/django-tinymce

Example
------------

.. image:: http://screencloud.net//img/screenshots/cef8f4c816e1cc7e9e1b08339eb3235c.png
django-editor 0.1
Allows pluggable WYSIWYG editors in django admin without hard dependencies
License: BSD

Django-editor
==========================

.. image:: https://secure.travis-ci.org/littlepea/django-editor.png
    :target: http://travis-ci.org/littlepea/django-editor

Allows pluggable WYSIWYG editors in django admin without hard dependencies.

Currently supported editors (both optional):

* `django-imperavi`_
* `django-tinycme`_

Installation
------------

1. Install with pip::

    pip install django-editor

2. (optional) Add `imperavi` or `tinymce` to your INSTALLED_APPS in `settings.py`::

    INSTALLED_APPS = (
        ...
        # Imperavi (or tinymce) rich text editor is optional
        'imperavi',
    )

Usage
-----

`editor` package gives you the following replacement classes:

* `django.forms.widgets.Textarea` => `editor.EditorWidget` (becomes `ImperaviWidget` or `TinyMCE`)
* `django.contrib.admin.ModelAdmin` => `editor.EditorAdmin` (becomes `ImperaviAdmin` or stays as `ModelAdmin`)
* `django.contrib.admin.StackedInline` => `editor.EditorStackedInline` (becomes `ImperaviStackedInline` or stays as `StackedInline`)

Here are some examples on how to easily turn your Textareas into WYSIWYG editors::

    # admin.py
    from django.db import models
    from django.contrib import admin
    from editor.admin import EditorAdmin, EditorWidget, EditorStackedInline


    class MyInlineAdmin(EditorStackedInline): # StackedInline example
        model = Model1


    class MyModel2Admin(EditorAdmin): # ModelAdmin example
        inlines = [MyInlineAdmin]

    admin.site.register(Model2, MyModel2Admin)


    class MyModel3Admin(admin.ModelAdmin):
        formfield_overrides = {
            models.TextField: {'widget': EditorWidget},
        }

    admin.site.register(Model3, MyModel3Admin)

Credits
-------

- `django-imperavi`_
- `django-tinycme`_
- `modern-package-template`_
- `django-newsletter`_ for providing pluggable editor code idea

.. _`modern-package-template`: http://pypi.python.org/pypi/modern-package-template
.. _django-imperavi: https://github.com/vasyabigi/django-imperavi
.. _django-tinycme: https://github.com/aljosa/django-tinymce
.. _django-newsletter: https://github.com/dokterbob/django-newsletter


.. This is your project NEWS file which will contain the release notes.
.. Example: http://www.python.org/download/releases/2.6/NEWS.txt
.. The content of this file, along with README.rst, will appear in your
.. project's PyPI page.

News
====

0.2a1
-----

*Release date: UNRELEASED*

* Working on more editors. Stay tuned...


0.1
---

*Release date: 19-Mar-2013*

* Initial release
* Supports django-imperavi and django-tinycme
* 3 admin classes: EditorAdmin, EditorWidget, EditorStackedInline
* Test coverage
hydrat 0.9.5
Classifier comparison framework
License: BSD
Keywords: machinelearning textclassification documentprocessing

hydrat - Classifier Comparison Framework
==========================

This is the hydrat classifier comparison framework.

Credits
-------

- `Distribute`_
- `Buildout`_
- `modern-package-template`_

.. _Buildout: http://www.buildout.org/
.. _Distribute: http://pypi.python.org/pypi/distribute
.. _`modern-package-template`: http://pypi.python.org/pypi/modern-package-template


News
====

0.9.4
-----
*Release date: 8-11-2012*

* First "release" of hydrat in a long time. Development has continued, but there has not been an "official release" in awhile.
* This release is intended to support my publication of a langid test harness.

0.9.2.4
-------

*Release date: 16-10-2010*

* Developed the cherrypy-based store browser. The browser is invoked via 'hydrat browse <file.h5>'
** Split into subcomponents
** Added result deletion via the browser
** Added result-set comparison, showing instances misclassified in a set of results
** Added intelligent class-space reduction in displaying a result's class-class confusion matrix
* Added an xmlrpc server to the online framework. Classification as a service!
* Added merge capabilities to store
* Fixed a missing dependency on pexpect


0.9.2.3
-------

*Release date: 12-10-2010*

* Removed ~ from the paths considered in autoconfigure
* Made weka easier to autoconfigure
* Added -s to 'hydrat configure' to allow user to specify directories to scan

0.9.2.2
-------

*Release date: 12-10-2010*

* Improved the CLI options for 'hydrat browse'
* Simplified the Store management in Framework
* Added example code for the ALTW2010 Programming Competition

0.9.2.1
-------

*Release date: 11-10-2010*

* Fixed a subtle bug in the computation of cosine values.

0.9.2
-----

*Release date: 10-10-2010*

* Extensive work done on many fronts.
django-loading 0.1.1
Load your django apps by app name rather than module path.
License: BSD

===========
Django-loading
===========

.. image:: https://secure.travis-ci.org/RichardOfWard/django-loading.png
    :alt: Build Status
    :target: http://travis-ci.org/RichardOfWard/django-loading


Django-loading allows you to load your django apps by their app name rather
than by the module path. This is particularly useful if you don't know where
modules will be installed or if you plan to allow overriding of your apps (eg
a user replaces your ``foo.bar`` app with ``myfoo.bar``).


Usage
=====

If you have a django app called ``bar`` in a package called ``foo`` (such that
you would add ``foo.bar`` to your INSTALLED_APPS) then you can get hold of
``bar`` without knowing its full module path::

    import loading.apps.bar

Django-loading hooks into python's regular import mechanism so all the normal
ways to import things will work::

    from loading.apps.bar import models
    from loading.apps.bar.models import MyModel as ThisIsMyModel

Your app names in a django project should all be unqiue, django-loading won't
work if they are not (but django won't like that either).


Installation
============

Use your favorite install method, for example:

    $ pip install django-loading

You do not need to add django-loading to your INSTALLED_APPS, just start using
it.
rose 1.0.0
A small library for keeping your version up-to-date easily & everywhere.
License: BSD

====
rose
====

"""A version by any other name would be just as sweet."""

A small library for keeping your version up-to-date easily & everywhere.

The pain of having to update your ``setup.py``, your Sphinx ``conf.py``, your
``__init__.py`` & everything else on every release of your Python package sucks.
Make your life easier (& very semver_!)

.. _semver: http://semver.org/

By putting your version number in a top-level VERSION file & using this library,
you can cut duplication & tedious manual work **without** having to lean on
crazy import hacks.

Inspired by crazy discussion with George Hickman (ghickman) at PyCon 2013.


Requirements
============

* Python 2.5+


Usage
=====

To start, first install ``rose`` (see below). Then, push your version
number into it's own file (typically called ``VERSION``)::

    $ echo '1.0.0-beta' > VERSION

Update your ``setup.py`` to look like::

    # ...

    import rose

    setup(
        name='your_package_name_here',
        # UPDATE THIS LINE!
        version=rose.load_version('VERSION'),
        # The usual follows...

Then update your ``__init__.py``::

    # Whatever is there, then...

    import os
    import rose

    # If you don't care about being cross-platform, you can just pass a simple
    # path instead.
    VERSION_FILE = os.path.join(os.path.dirname('VERSION'))
    __version__ = rose.build_version('your_package_name_here', rose.load_version(VERSION_FILE))

And if you're documenting with Sphinx, you can update your ``conf.py`` with::

    # ADD THIS!
    import rose
    RELEASE_VERSION = rose.load_version('../VERSION')
    SHORT_VERSION = RELEASE_VERSION.split('-')[0]

    # The version info for the project you're documenting, acts as replacement for
    # |version| and |release|, also used in various other places throughout the
    # built documents.
    #
    # The short X.Y version.
    version = SHORT_VERSION
    # The full version, including alpha/beta/rc tags.
    release = RELEASE_VERSION


Installation
============

Using ``pip``, simply run::

    pip install rose


License
=======

New BSD