semvec/pypi-packages huggingface dataset:
jiraprinter 0.0.1
Simple printing interface for jira
License: MIT
Keywords: jira printing

jira ticket printer
===================

Jira does not provide a nice printable layout for tickets and nicer
printing options are costly. This script just wraps the jira-api to
allow formatting using jinja2 templates. This way, tickets can easily be
formatted in a printer friendly way.

Getting started
---------------

The jiraprinter works on python3 only.

Jiraprinter is on pypi, so you can simply run

::

    pip install jiraprinter

To install it. This will also create the two commands ``jira.py`` and
``prepare_token`` used below.

You can run the command line tool by calling

::

    $ jira.py export <Ticket-Id> [<Ticket-Id> ...]

Here, angle brackets (``<>``) denote variable parameters and square
brackets (``[]``) denote optional parameters. This is similar to unix
``man`` pages. You can start the web-interface for selecting tickets and
printing them by calling

::

    $ jira.py select

The web-interface will then be available at ``localhost:8080``.

Setting your credentials
------------------------

It is recommended that you put the URL of your jira server as well as
your credentials into separate environment variables. Your user
credentials need to be passed in base 64 encoding, which can be done
using the ``prepare_token.py`` script:

::

    $ prepare_token.py
    Please enter your jira user name: myname
    Please enter your jira password:
    fowkeofoakjdfolai

That last name is your jira credentials in base 64 encoding. It is
recommended that you set your jira credentials and the url of the server
in your bashrc (if you use bash). To do so, add the following lines to
your ``~/.bashrc`` file.

::

    export JIRAURL=https://jira.mycompany/rest/api/2
    export JIRACREDENTIALS=fowkeofoakjdfolai

Obviously, both the URL and the credentials are completely made up.

Authentication error
--------------------

Error messages are typically rather long and complex. If you see a 401
status code somewhere at the end of the stacktrace, that means that
you're not correctly authenticated. In that case, you might want to
check your user name and password.

Travis
------

Test status on current master: |build status|

.. |build status| image:: https://travis-ci.org/igordertigor/jiraprinter.svg?branch=master
whenis 0.0.2
A command-line utility to convert timestamps between UTC and local timezones.
License: MIT
Keywords: time zone timezone conversion

whenis
======

**whenis** is a command-line utility that converts timestamps between
UTC and local timezones.

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

::

    pip install whenis

Usage
-----

::

    $ whenis -h
    usage: whenis [-h] [-f TIMEZONE] [-t TIMEZONE] [timestamp [timestamp ...]]

    Convert timestamps between UTC and local timezones.

    positional arguments:
      timestamp             timestamp to be converted

    optional arguments:
      -h, --help            show this help message and exit
      -f TIMEZONE, --from TIMEZONE
                            timezone to convert from (default: utc)
      -t TIMEZONE, --to TIMEZONE
                            timezone to convert to (default: local)

    $ whenis -f utc -t local "12/7/16 1:28:36.156 AM"
    Tue 6 Dec 2016, 5:28:36 PM -08:00

    $ whenis 2016-12-07 01:28:36,156
    Tue 6 Dec 2016, 5:28:36 PM -08:00

    $ whenis -f local -t utc 6 Dec 2016, 5:28:36 PM
    Wed 7 Dec 2016, 1:28:36 AM +00:00

License
-------

`MIT <http://opensource.org/licenses/MIT>`__
django-werkzeug 1.0.0
Enhances Django runserver with Werkzeug.
License: MIT

Django Werkzeug
===============

[![Current version on PyPI](http://img.shields.io/pypi/v/django-werkzeug.svg)][pypi]

Enhances Django `runserver` with [Werkzeug][].

This project uses [Django Extensions][] under the hood. It "wraps" it, along
with Werkzeug, so you don't have to add an explicit `werkzeug` dependency
to your `requirements.txt` or remember a new command.


Why
---

Werkzeug and its builtin error page has proven to be indispensable in a number
of Django projects. While Django Extensions is also a great tool, the full
extent of it is not always needed in specific projects.

Also, when committing to Werkzeug, it's convenient to run the `runserver`
instead of learning a new command. This brings newcomers to your team up to
speed without further instruction and doesn't require existing members to
change their muscle memory during their day-to-day.

If you want to use Werkzeug on certain projects, but don't want to keep track
of which ones, this package is for you.


Requirements
------------

Django Werkzeug requires Django 1.8 or later.


Installation
------------

```bash
$ pip install django-werkzeug
```

Then enable it by adding it to `INSTALLED_APPS` in your `settings.py` file:

```python
INSTALLED_APPS = [
    'django_werkzeug',
    ...
]
```


Usage
-----

```bash
$ python manage.py runserver
```

Or to run Django's classic builtin server, run:

```bash
$ python manage.py runserver_classic
```


Contributing
------------

1. Check the open issues or open a new issue to start a discussion around
   your feature idea or the bug you found
2. Fork the repository and make your changes
3. Create a new pull request


[pypi]: http://pypi.python.org/pypi/django-werkzeug/
[werkzeug]: https://github.com/pallets/werkzeug
[django extensions]: https://github.com/django-extensions/django-extensions