semvec/pypi-packages huggingface dataset:
tox-nuitka 0.0.1
A nuitka plugin for tox
License: MIT

tox-nuitka
==========

.. image:: https://img.shields.io/pypi/v/tox-nuitka.svg
        :target: https://pypi.python.org/pypi/tox-nuitka

.. image:: https://img.shields.io/travis/tonybaloney/tox-nuitka.svg
        :target: https://travis-ci.org/tonybaloney/tox-nuitka

.. image:: https://codecov.io/gh/tonybaloney/tox-nuitka/branch/master/graph/badge.svg
        :target: https://codecov.io/gh/tonybaloney/tox-nuitka

.. image:: https://pyup.io/repos/github/tonybaloney/tox-nuitka/shield.svg
     :target: https://pyup.io/repos/github/tonybaloney/tox-nuitka/
     :alt: Updates

.. image:: https://pyup.io/repos/github/tonybaloney/tox-nuitka/python-3-shield.svg
     :target: https://pyup.io/repos/github/tonybaloney/tox-nuitka/
     :alt: Python 3

A tox plugin to replace the default use of the CPython compiler with nuitka.

This plugin works by injecting Nuitka as a pip requirement to all test environments and then adding the Nuitka
compile as a pre-test stage.

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

.. code-block:: bash

    pip install tox-nuitka

Or, 

.. code-block:: bash

    pipenv install tox-nuitka  

Executing tests
---------------

Each of the commands in your testenv configuration will be compiled by nuitka to execute within the pipenv virtual environment

Example tox.ini
---------------

This simple example will run pytest against your package but compile myapp/main.py using Nuitka.

.. code-block:: 

        [tox]
        envlist = py27, py36, py37

        [testenv]
        nuitka = myapp/main.py
        deps = pytest
        commands = python -m pytest test/

Additional Nuitka configuration is available within the test environment settings.

Currently, the --module and --recurse-all flags are available like this:

.. code-block:: 

        nuitka_module = true
        nuitka_recurse_all = true

Multiple compile targets can be provided

.. code-block:: 

        nuitka = 
                myapp/target1.py
                myapp/target2.py

Release notes
=============

1.0.0 (date)
------------------

* Feature
CityTime 1.0.0
A tool for comparing time between different locations/timezones
License: MIT
Keywords: time datetime olson timezone

CityTime
########

.. image:: https://img.shields.io/codecov/c/github/tweyter/CityTime.svg
    :target: https://codecov.io/gh/tweyter/CityTime

.. image:: https://travis-ci.org/tweyter/CityTime.svg
    :alt: CityTime Build status
    :target: https://travis-ci.org/tweyter/CityTime

Thanks:
/u/phira

The CityTime object is my solution for the headache of time zones and daylight savings time.  It takes
the local time and the local time zone, and translates the time into UTC.  The time can then be reproduced
in various formats and also incremented forward and back while still adjusting for daylight savings time.

CityTime is a tool for comparing the time in two different cities. For example, let's say it is 5pm in New York
and 4pm in Chicago. CityTime will take both of those times and time zones, convert them to UTC, and by comparing
the two CityTime objects, will tell you if they are the same time or not (in this case, they are).

Let's say it's 8pm in Tokyo on November 1 (UTC + 9), and 7am in New York on the same date (UTC - 4). If you
create a CityTime object for each city, and compare the two, it will show that they are the same. However,
if you tried the same thing on November 3 (after Daylight Savings Time ends), they will be different,
because Japan does not follow Daylight Savings Time.

CityTime handles cases like those mentioned above by converting the input local time to UTC, while storing
the Olson Database time zone, rather than just using a UTC offset. This way, local differences in the start
and end of Daylight Savings Time are accounted for.

A CityTime object can be instantiated using a datetime.datetime object, an ISO8601 string, or another
CityTime object. If instantiated using an ISO8601 string, the time used must be UTC, it will not work
with a localized time.