semvec/pypi-packages huggingface dataset:
sentry-unfuddle 1.0.1
A Sentry extension which creates Unfuddle issues from sentry events.
License: BSD

sentry-unfuddle
===============

A flexible extension for Sentry which allows you to create issues in
Unfuddle based on sentry events. It is based off the implementation for
`sentry-jira <https://github.com/getsentry/sentry-jira>`__.

Currently it works with Sentry 7 and 8.

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

The sentry-unfuddle module is `published on the Python Package
Index <https://pypi.python.org/pypi/sentry-unfuddle>`__, so you can
install it using ``pip`` or ``easy_install``.

::

    pip install sentry-unfuddle

Or:

::

    easy_install sentry-unfuddle

This is a server plugin, so it needs to be installed into the same
Python environment you are running your Sentry instance from.

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

Go to your project's configuration page (``Projects -> [Project]``) and
select the Unfuddle tab. Enter the Unfuddle credentials and Project
configuration and save changes. Filling out the form is a two step
process (one to fill in your instance details and credentials, one to
select the project to link to).

The user you add on the configuration screen is the one used to process
API requests, so ensure that user has ``Account Administrator`` or at
the very least ``Project Administrator`` privileges.

Usage
=====

Once configured, users will see a link to "Create Unfuddle issue" on the
event page. Clicking on that brings you to a page in which you can
select a user to assign the issue to, select an upcoming milestone, and
select a priority (defaults to ``High``.) The "title" and "description"
fields are prepopulated with the data from the event.

The plugin will try to be smart when creating an issue on Unfuddle. If
it finds a user that matches the currently logged in Sentry user, it
will make that user the reporter of the ticket (if no match, defaults to
the user from the configuration page.)

License
=======

``sentry-unfuddle`` is licensed under the terms of the 3-clause BSD
license.

Contributing
============

All contributions are welcome, including but not limited to:

-  Documentation fixes / updates
-  New features (requests as well as implementations)
-  Bug fixes (see issues list)

If you encounter any errors in the code, please file an issue on github:
https://github.com/rkeilty/sentry-unfuddle/issues.

Author
======

-  Author: Rick Keilty
-  Email: rkeilty@gmail.com
-  Repository: http://github.com/rkeilty/sentry-unfuddle

Version
=======

-  Version: 1.0.1
-  Release Date: 2016-01-23

Revision History
================

Version 1.0.1
-------------

-  Release Date: 2016-01-23
-  Changes:

   -  Updated documentation
   -  Confirmed working with Sentry 8.0.x

Version 1.0.0
-------------

-  Release Date: 2015-12-07
-  Changes:

   -  Updated documentation
   -  Made version 1.0.0, as this has been running successfully in
      several production environments.

Version 0.11.0
--------------

-  Release Date: 2015-12-06
-  Changes

   -  Initial port of
      `sentry-jira <https://github.com/getsentry/sentry-jira>`__ to
      `sentry-unfuddle <https://github.com/rkeilty/sentry-unfuddle>`__
lpbm 2.0.0
Lightweight personal blog maker
License: BSD

Lightweight Personal Blog Maker
===============================

This project aims to provide an easy way to generate static blog and personal
website using python scripts. Every page of the site is written using markdown,
to help formatting easily text.

This project is still under heavy development, and a lot of things aren't
fixed yet (meaning configuration file can change rapidly and often, for
example). Don't use it right now if you are not willing to spend some time fix
things between big updates.

This file only contains the minimum you need to know to install LPBM. A more
detailed documentation is provided in `doc/` directory, as a sphinx
documentation.

Features
--------

* LPBM is split in several sub-modules. Including configuration management,
  articles management, authors management and blog generation.
* You only need to know markdown to write articles. Every meta-data is stored
  in ini files, meaning you can manage them with any CVS.
* You can have any number of authors on articles, and any number of categories.
* Simple code embedding into articles. (using pygments).

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

LPBM will soon be packaged with setup.py and PKGBUILD, and I will put it in AUR
too, when it will be ready for a Release Candidate.

### Install LPBM as a script.

For know, you can just clone this repository and link `~/.local/bin/lpbm` to
the lpbm.py file. Then you add `$HOME/.local/bin/` to your `PATH` environment
variable and you can execute LPBM everywhere.

### Install dependencies

You also must install `python` version 3, `pip` for python version 3 and all
the python library dependencies. To do this, you just have to execute `pip
install -r requirements.txt` and you'll have everything you need.

Usage
-----

There will be a detailed description of all the features and the usage of all
commands in the sphinx documentation in `doc/` directory.

Other information
-----------------

### Authors (v2)

* [Franck Michea](http://blog.kushou.eu/)

### Authors (v1)

* [Franck Michea](http://blog.kushou.eu/)
* [Pierre Bourdon](http://blog.delroth.net/)

### LPBM generates this blog:

* [LSE Blog](http://blog.lse.epita.fr/)

### Useful Links

* [Markdown Syntax](http://daringfireball.net/projects/markdown/syntax)
* [Code Embedding](http://packages.python.org/Markdown/extensions/code_hilite.html)
* [LPBM Documentation](http://kushou.eu/lpbm-doc/)
more.chameleon 0.2
Chameleon template integration for Morepath
License: BSD
Keywords: morepath chameleon

more.chameleon: Chameleon template integration for Morepath
===========================================================

``more.chameleon`` is an extension for Morepath_ that adds Zope Page
Template (ZPT) support for the ``.pt`` extension, using the Chameleon_
template engine.

For details on the ZPT template language see the `Chameleon language
reference`_.

Example usage::

  from more.chameleon import ChameleonApp

  class App(ChameleonApp):
      pass

  @App.path(path='persons/{name}')
  class Person(object):
       def __init__(self, name):
           self.name = name

  @App.template_directory()
  def get_template_directory():
      return 'templates'

  @App.html(model=Person, template='person.pt')
  def person_default(self, request):
      return {'name': self.name}

and then in ``person.pt`` (in the ``templates`` subdirectory)::

  <html>
  <body>
  <p>Hello ${name}!</p>
  </body>
  </html>

During development it can be helpful to have Chameleon reload templates
automatically after a change. To enable this feature use the
``MOREPATH_TEMPLATE_AUTO_RELOAD`` environment variable.

You can enable it for your process::

  MOREPATH_TEMPLATE_AUTO_RELOAD=1 python run.py

Or for your shell::

  export MOREPATH_TEMPLATE_AUTO_RELOAD=1
  python run.py

To further control Chameleon rendering you can define a ``chameleon`` setting
section in your app. For instance, here is how you turn on Chameleon's
``debug`` functionality::

  @App.setting_section(section='chameleon')
  def get_setting_section():
      return {'debug': True}

For details on Chameleon configuration options, consult the
configuration keyword arguments in the `Chameleon API reference`_.

.. _Morepath: http://morepath.readthedocs.org

.. _Chameleon: https://chameleon.readthedocs.org/

.. _`Chameleon language reference`: https://chameleon.readthedocs.org/en/latest/reference.html

.. _`Chameleon API reference`: https://chameleon.readthedocs.org/en/latest/library.html#api-reference

CHANGES
*******

0.2 (2016-01-23)
================

- The ``MOREPATH_TEMPLATE_AUTO_RELOAD`` environment variable may now be used
  to control the auto reloading behavior of Chameleon.

  See README.rst for details.

  Fixes Issue #1: https://github.com/morepath/more.chameleon/issues/1


0.1 (2015-04-09)
================

- Initial public release.