semvec/pypi-packages huggingface dataset:
django-storymarket 1.0a3
Sync Django models to Storymarket.
License: BSD

Django bindings to the Storymarket API
======================================

This library binds Django models to the `Storymarket API
<http://storymarket.com/api/v1/>`_.

You'll need a Storymarket account to use this library, and you'll need to
generate an API token by visiting the 
`Developer API page <http://storymarket.com/users/api/>`_.

.. warning::

    This library is, at best, of beta quality. It works, but is
    under-tested and -documented, prone to API changes, and likely has
    bugs. At this point in time it should be considered a sketch, not
    a finished work.

Documentation
-------------

`Read the documentation <http://packages.python.org/django-storymarket/>`_.
See also `the python-storymarket documentation
<http://packages.python.org/python-storymarket/>`_

Contributing
------------

Run tests with ``python setup.py test``.

Development takes place 
`on GitHub <http://github.com/jacobian/django-storymarket>`_; please file
bugs/pull requests there.

Development on this project was funded by the 
`Lawrence Journal-World <http://ljworld.com/>`_ - thanks!
TracGoogleAds 0.2.2
Trac plugin designed to display ads on your Trac environment
License: BSD
Keywords: trac plugin google ads

TracGoogleAds
=============

Previously known as `Trac Ads Panel`_, TracGoogleAds_ is a trac_ plugin designed
to display ads on your trac_ environment.

The main feature of the plugin is that it allows the user to persistently_
hide the ads, making your trac_ environment less annoying to those who
dislike ads and supporting open-source projects through them.

*Plugin has been renamed and package hierarchy has changed to join*
`other trac plugins`_ *that addressed* Google_ *services.*

Installation
------------
Installing the plugin is as easy as::

  sudo easy_install TracGoogleAds

And then enabling it:

::

  [components]
  tracext.google.ads.* = enabled

And that's it!

Now, all you have to do is to go to the administration and under **Google**
you have a **Ads** link to setup the plugin.

Bugs and/or New Features
------------------------

Please submit bugs of new features to::

  http://google.ufsoft.org/


Source Code
-----------

If you wish to be on the bleeding edge and get the latest available code:

::

  hg clone http://google.ufsoft.org/hg/ads/ TracGoogleAds


**Note**: For up-to-date documentation please visit TracGoogleAds_'s site.

~~~~

.. [persistently] *The user choice of hiding the ads will remain untouched
                  throughout it's later visits, and he'll still have the
                  choice to display them again*.

.. _trac: http://trac.edgewall.org
.. _TracGoogleAds: http://google.ufsoft.org/wiki/TracGoogleAds
.. _other trac plugins: http://google.ufsoft.org/
.. _Google: http://www.google.com
.. _Trac Ads Panel: http://devnull.ufsoft.org/wiki/TracAdsPanel
mobi.interfaces 1.0
Mobile libs interfaces package
License: BSD

===============
mobi.interfaces
===============


Interfaces package for mobi.* libs.
see ``mobi.devices`` for more info.


Changelog
=========

mobi.interfaces 1.0 (2010-09-13)
--------------------------------

* release

mobi.interfaces 1.0b1 (2010-07-14)
----------------------------------

* first release, see README.txt
django-extracontent 0.1
A django abstract model and form for handling extra content in a model.
License: BSD

:Dowloads: http://pypi.python.org/pypi/django-extracontent/
:Source: http://github.com/lsbardel/django-extracontent
:Keywords: django, database

--

A django abstract model and form for handling extra content in a model.

Let's say we have a model ``MyData`` which can point to different underlying data types::
	
	from django.db import models
	from extracontent.models import ExtraContent
	from extracontent.forms import ExtraContentForm
	
	class DataModel1(models.Model):
	    value = models.TextField()
		
	class DataModel2(models.Model):
	    dt = models.DateField()
		
	class MyData(ExtraContent):
	    name = models.CharField(max_length = 20)
	
	class MyDataForm(ExtraContentForm):
	    class Meta:
	        model = MyData
	
	
Then we can do this::

	>>> from extracontent import content
	>>> elem = MyDataForm({'content_type':content('datamodel1'),
	... 'value':'this is a test', name:'a data object'}).save()
	>>> elem.extra_content()
	<DataModel1: DataModel1 object>
	>>> elem.extra_content().value
	'this is a test'
	
	

Running Tests
====================
Once installed::

	>>>from extracontent.tests import run
	>>>run()
	
or from within the ``tests`` directory::

	python runtests.py
pypi-tools 0.0.2
Command line PyPI search tool
License: BSD
Keywords: pypi search

==========
pypi-tools
==========

Package pypi-tools contains now only one script called ``pypi``.
It is command line utility for searching in Python Package Index.

Usage
=====

Let's find something. What about some django gravatar application?

    $ pypi django avatar
    $ 

Hmm, nothing. Ok, maybe just gravatar? :)

    $ pypi gravatar
    django-gravatar                - Gravatar Support in a Django Reusable Application
    gravatar                       - Gravatar generator. Includes all API parameters included in their documentation.
    tw.gravatar                    - inserts gravatar images
    tw.gravatar                    - inserts gravatar images

Cool. It found something. Duplicated tw.gravatar line looks like a bug :)

Let's see what is tw.gravatar.

    $ pypi -s tw.gravatar
     name:                tw.gravatar
     summary:             inserts gravatar images
     version:             0.1a0dev-20100727
     author:              Nicolas Laurance
     author_email:        nicolas[dot]laurance<at>gmail.com
     keywords:            toscawidgets.widgets,gravatar
     classifiers:         Development Status :: 3 - Alpha
                          Environment :: Web Environment
                          Environment :: Web Environment :: ToscaWidgets
                          Framework :: TurboGears :: Widgets
    ...

Ooops, it is not django application.

``pypi`` command understand complex search queries. You can see the list of search
operators in ``pypi -h`` output.

Here is example of searching all crap I have uploaded on the Python Package Index:

    lorien@big:/web/pypi-tools$ ./pypi --author_email lorien@lorien.name
    django-account                 - Django application for registration and authentication
    django-bookmarker              - Social bookmark linsk
    django-common                  - A number of useful django shortcuts and helpers
    ...
bp.tagging 0.3
Multimedia file tagging library
License: BSD
Keywords: mp3 mp4 id3

bp.tagging contains a set of convenience wrappers for mutagen
as well as a single command line script for basic ID3 tag manipulation.

Command line usage
==================

 -  bp_tagging COMMAND [ARGS...]
 -  bp_tagging help [COMMAND]

Options
*******

    -h, --help
        show this help message and exit

Commands
********

    help (?)
        give detailed help on a specific sub-command

    info (i)
        print available metadata for files

        Usage
            bp_tagging info [PATHS...]

        Options
            -h, --help
                show this help message and exit
            -v, --verbose
                print extra information
            -d, --debug
                print debug information


    remove_tag (rmt)
        completely remove TAG from files.

        Usage
            bp_tagging remove_tag TAG [PATHS...]

        Options
            -h, --help
                show this help message and exit
            -v, --verbose
                print extra information
            -d, --debug
                print debug information


    remove_tag_with_content (rmtc)
        remove tags with value PATTERN from files.

        Usage
            bp_tagging remove_tag_with_content PATTERN [PATHS...]

        Options
            -h, --help
                show this help message and exit
            -v, --verbose
                print extra information
            -d, --debug
                print debug information


    replace_in_tag (rpt)
        replace PATTERN with REPLACEMENT in TAG on files. Use 'all' for tag to replace in all tags.

        Usage
            bp_tagging replace_in_tag TAG PATTERN REPLACEMENT [PATHS...]

        Options
            -h, --help
                show this help message and exit
            -v, --verbose
                print extra information
            -n, --nosave
                don't save (only print what would be done).
            -d, --debug
                print debug information


    tag (t)
        get/set the VALUE for TAG on files.

        Usage
            bp_tagging tag TAG [VALUE [PATHS...]]

        Options
            -h, --help
                show this help message and exit
            -v, --verbose
                print extra information
            -s, --set
                set the tag value
            -d, --debug
                print debug information





Changelog
=========

0.3
***

-   completely revised command line usage (not compatible with prior versions!)

-   switched from Baker to cmdln


0.2
***

-   Added preference infarastructure
    (using http://pypi.python.org/pypi/bp.preferences)

-   Added filename_from_tags property to File

-   Expose filename_from_tags as tags2filename command


0.1.1
*****

-   Recreated the project with modern-package-template
    (http://pypi.python.org/pypi/modern-package-template/1.0).


0.1
***

- Initial release
dm.zope.rpc.wsdl_suds 0.2a1
WSDL described SOAP protocol support for "dm.zope.rpc", based on "suds"
License: BSD
Keywords: rpc zope multiprotocol soap wsdl

This is a plugin for ``dm.zope.rpc``, a protocol independent
middleware to expose web services over a variety of rpc protocols.

This package is using ``suds``, an advanced soap (1.1) client library under
the LGPL license.
``suds`` is slightly abused by using it to implement a server component.
This abuse requires the use of undocumented implementation details
which may change between ``suds`` versions. The package has been
implemented with ``suds==0.3.9``. It may not work with other versions.


Limitations
===========

The current implementation does not handle exceptions.
They are not transformed into SOAP ``Fault`` messages (as required
by SOAP 1.1) but
reported by the underlying transport protocol ("HTTP") (using
HTTP error codes with HTML messages).
The reason for this limitation: SOAP 1.1 has no complete
(self contained) specification for its ``Fault`` element but requires
externally defined namespaces for completion and I have not yet
understood the interaction between WSDL defined exceptions and
SOAP ``Fault`` elements. Once, I have understood WSDL specified
exceptions, this limitation might be removed.

SOAP and WSDL are complex standards with a large number of features.
This package does not support all features. For example, it
ignores all SOAP headers, even headers with a ``must_understand``
declaration (in violation of the SOAP specification).
In addition, only a small set of features has been tested:
for example, only the ``document`` binding; other bindungs might
(or might not) work. Over time, more features might be supported,
might have been tested.

The current implementation makes use of ``suds`` WSDL caching. This
can be confusing during WSDL development, as modifications are not
seen until the cache times out. Delete the ``suds`` cache files in such
a case (they usually are in a ``suds`` subfolder of the folder typically
used for temporary files).



Configuration
=============

As usual with ``dm.zope.rpc`` protocol handlers, configuration
is via a marshaller instance.
The WSDL specific configuration of the  ``WsdlMarshaller`` is
via the fields ``wsdl_map`` and ``default_namespace``.
``wsdl_map`` maps the namespace found in a method invocation to
an url which provides access to the WSDL for this namespace.
``default_namespace`` is the namespace to be used for GET requests
when method and parameters are specified directly in the url and
not via a request entity.

You can find a (simple) example configuration in ``tests.soap``.


Misc
====

The package has been tested under Zope 2.12 and Zope 2.10.
For Zope versions before 2.12, a properly configured
``dm.zopepatches.xmlrpc`` is required, to prevent Zope's
builtin xmlrpc support to interfere. The above mentioned example
configuration shows how ``dm.zopepatches.xmlrpc`` can be configured.
dm.zope.rpc_protocol.wsdl_suds 0.1a2
WSDL described SOAP protocol support for "dm.zope.rpc", based on "suds"
License: BSD
Keywords: rpc zope multiprotocol soap wsdl

This is a plugin for ``dm.zope.rpc``, a protocol independent
middleware to expose web services over a variety of rpc protocols.

This package is using ``suds``, an advanced soap (1.1) client library under
the LGPL license.
``suds`` is slightly abused by using it to implement a server component.
This abuse requires the use of undocumented implementation details
which may change between ``suds`` versions. The package has been
implemented with ``suds==0.3.9``. It may not work with other versions.


Limitations
===========

The current implementation does not handle exceptions.
They are not transformed into SOAP ``Fault`` messages (as required
by SOAP 1.1) but
reported by the underlying transport protocol ("HTTP") (using
HTTP error codes with HTML messages).
The reason for this limitation: SOAP 1.1 has no complete
(self contained) specification for its ``Fault`` element but requires
externally defined namespaces for completion and I have not yet
understood the interaction between WSDL defined exceptions and
SOAP ``Fault`` elements. Once, I have understood WSDL specified
exceptions, this limitation might be removed.

SOAP and WSDL are complex standards with a large number of features.
This package does not support all features. For example, it
ignores all SOAP headers, even headers with a ``must_understand``
declaration (in violation of the SOAP specification).
In addition, only a small set of features has been tested:
for example, only the ``document`` binding; other bindungs might
(or might not) work. Over time, more features might be supported,
might have been tested.

The current implementation makes use of ``suds`` WSDL caching. This
can be confusing during WSDL development, as modifications are not
seen until the cache times out. Delete the ``suds`` cache files in such
a case (they usually are in a ``suds`` subfolder of the folder typically
used for temporary files).



Configuration
=============

As usual with ``dm.zope.rpc`` protocol handlers, configuration
is via a marshaller instance.
The WSDL specific configuration of the  ``WsdlMarshaller`` is
via the fields ``wsdl_map`` and ``default_namespace``.
``wsdl_map`` maps the namespace found in a method invocation to
an url which provides access to the WSDL for this namespace.
``default_namespace`` is the namespace to be used for GET requests
when method and parameters are specified directly in the url and
not via a request entity.

You can find a (simple) example configuration in ``tests.soap``.


Misc
====

The package has been tested under Zope 2.12 and Zope 2.10.
For Zope versions before 2.12, a properly configured
``dm.zopepatches.xmlrpc`` is required, to prevent Zope's
builtin xmlrpc support to interfere. The above mentioned example
configuration shows how ``dm.zopepatches.xmlrpc`` can be configured.