semvec/pypi-packages huggingface dataset:
scsgate 0.1.0
A Python module to interact with SCSGate
License: MIT
Keywords: scsgate home-automation development

scsgate |Build Status| |Docs|
=============================

This python module allows to interact with a
`SCSGate <https://goo.gl/aKnpDw>`__ device.

The module has been written to manage a SCSGate device with
`home-assistant <https://home-assistant.io/>`__.

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

The scsgate module can be installed using pip:

::

    sudo pip install scsgate

Monitoring the SCS bus
----------------------

The scsgate pip package provides a script named ``scs-monitor`` that has
two purposes:

-  interactively create a configuration file for home-assistant
-  sniff all the messages going over the SCS bus

Creation of a home-assistant configuration file
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

``scs-monitor`` can be used to create a home-assistant configuration
file defining all the available devices.

This can be done by using the ``--homeassistant-config`` flag.

Once started ``scs-monitor`` will start sniffing all the events going
over the SCS bus. For each captured message it will extract the ID of
the relevant device and will ask the user to enter an ID for
home-assistant and the name of the device.

By pressing ``CTRL-C`` the program will exit and generate the
home-assistant configuration file.

Sniffing messages
~~~~~~~~~~~~~~~~~

By defaul ``scs-monitor`` will print all the messages going over the SCS
buffer.

It's possible to filter the messages related with a list of known
devices. This can be done using the ``-f`` flag followed by the name of
the file containing the devices to ignore. The file is a yaml document
like the one created in the previous step.

It's also possible to redirect all the output to a text file by using
the ``-o`` flag.

License
~~~~~~~

This code is licensed under the MIT license.

.. |Build Status| image:: https://travis-ci.org/flavio/scsgate.svg?branch=master
   :target: https://travis-ci.org/flavio/scsgate
.. |Docs| image:: https://readthedocs.org/projects/scsgate/badge/?version=latest
   :target: http://scsgate.readthedocs.org/en/latest/?badge=latest
pip-init 0.3.0
pip-init to generate a base setup.py file
License: MIT

========
pip-init
========

.. image:: https://travis-ci.org/juanpabloaj/pip-init.svg?branch=master
    :target: https://travis-ci.org/juanpabloaj/pip-init

Generate a base setup.py file to upload a python package to `pypi <https://pypi.python.org/pypi>`_

Install
=======

::

    pip install pip-init

Usage
=====

::

    pip-init

.. image:: http://i.imgur.com/1Wg46cR.gif

I created a setup.py file, what are the next steps?
====================================================

What are the next steps to upload a package to `pypi <https://pypi.python.org/pypi>`_?

* Create or edit the python code of your package: ::

    mkdir package_code
    $EDITOR package_code/__init__.py

* Create an account on the `PyPI website <https://pypi.python.org/pypi?%3Aaction=register_form>`_.
* Create a ~/.pypirc file ::

    [pypi]
    repository = https://pypi.python.org/pypi
    username = <username>
    password = <password>

* Register and upload your package to pypi ::

    python setup.py register
    python setup.py sdist upload -r pypi

References
==========
* `Packaging and Distributing Projects, pypa. <https://packaging.python.org/en/latest/distributing.html>`_
* `Sharing Your Labor of Love: PyPI Quick and Dirty, Hynek Schlawack. <https://hynek.me/articles/sharing-your-labor-of-love-pypi-quick-and-dirty/>`_
* `Open Sourcing a Python Project the Right Way, Jeff Knupp. <http://www.jeffknupp.com/blog/2013/08/16/open-sourcing-a-python-project-the-right-way/>`_
* `Empaquetando y distribuyendo código python con pip (spanish), JuanPabloAJ. <https://speakerdeck.com/juanpabloaj/empaquetando-y-distribuyendo-codigo-python-con-pip>`_
* `setup.py vs requirements.txt, Donald Stufft. <https://caremad.io/2013/07/setup-vs-requirement>`_
* `Pypi classifiers list. <https://pypi.python.org/pypi?%3Aaction=list_classifiers>`_

Contributors
============

- `JuanPablo AJ <https://github.com/juanpabloaj>`_
- `David Yen <https://github.com/davidyen1124>`_
- `Tom Viner <https://github.com/tomviner>`_
- `Krisztián Fekete <https://github.com/krisztianfekete>`_
- `Kevin J. Qiu <https://github.com/kevinjqiu>`_
socialauth 0.2.0
A framework- and backend-independent social login provider.
License: MIT

Python Social Auth
==================

.. image:: https://travis-ci.org/emilyhorsman/socialauth.svg?branch=master
    :target: https://travis-ci.org/emilyhorsman/socialauth
    :alt: Travis CI

.. image:: https://coveralls.io/repos/github/emilyhorsman/socialauth/badge.svg?branch=master
    :target: https://coveralls.io/github/emilyhorsman/socialauth?branch=master
    :alt: Coveralls Test Coverage

.. image:: https://readthedocs.org/projects/socialauth/badge/?version=latest
    :target: http://socialauth.readthedocs.org/en/latest/?badge=latest
    :alt: Documentation Status

.. image:: https://codeclimate.com/github/emilyhorsman/socialauth/badges/gpa.svg
    :target: https://codeclimate.com/github/emilyhorsman/socialauth
    :alt: Code Climate

.. image:: https://img.shields.io/pypi/v/socialauth.svg
    :target: https://pypi.python.org/pypi/socialauth
    :alt: PyPI

.. image:: https://img.shields.io/badge/python-%E2%89%A5%203.3-blue.svg
    :target: https://docs.python.org/3/
    :alt: Python >= 3.3

.. image:: https://img.shields.io/badge/code%20of%20conduct-v1.3.0-4C1161.svg
    :target: CODE_OF_CONDUCT.md
    :alt: Contributor Covenant Code of Conduct

.. image:: https://img.shields.io/pypi/l/socialauth.svg
    :alt: MIT License


A library for social sign-in capability from providers such as Twitter and
Facebook.

Many social authentication solutions exist. I wanted something that didn’t
have strong ties to an HTTP framework or storage backend. Preferably, I
didn’t want something that dealt with a storage backend at all. This library
uses JSON web tokens instead of sessions to deal with intermediate information
in the OAuth flow (such as a token secret).

.. code-block:: bash

    $ pip install socialauth



Run Tests
=========

.. code-block:: bash

    $ git clone https://github.com/emilyhorsman/socialauth.git
    $ mkvirtualenv --python=python3 socialauth
    $ cd socialauth
    $ workon .
    $ pip install -r requirements.test.txt
    $ python tests.py

Build Docs
==========

.. code-block:: bash

    $ pip install -r requirements.docs.txt
    $ cd docs
    $ make html
mail_diff 1.0
Automatically mails your group members the local changes you make in your project
License: MIT
Keywords: python , linux ,  email

MailDiff
========

Automatically mails your group members the local changes you make in
your project

Installation
============

::

    >> pip install mail_diff

Usage:
======

::

    >> cd your_project_directory
    >> mail_diff

Then follow through the instructions

Examples:
=========

::

    >> cd Documents/scripts
    >> mail_diff
    Enter your Password: 
    sending mail to apndey.15@gmail.com .......
    mail sent

    sending mail to someone@gmail.com .......
    mail sent
pietroalbini-sphinx-themes 1.3.1
Sphinx themes for my own projects
License: MIT

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Pietro Albini's Sphinx themes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This repository contains the source code of my own base Sphinx_ theme,
released under the MIT license. Feel free to include it in your projects, even
if I ask you to customize them a little bit in order to avoid users confusion.

How to use the theme in your projects
=====================================

The package itself provides an utility function to get the absolute path of
the theme's directory. So, you can put this simple snippet in your
documentation's ``conf.py``::

   import pietroalbini_sphinx_themes
   html_theme_path = [pietroalbini_sphinx_themes.themes_path()]

   html_theme = "pietroalbini"

You don't need to provide a Pygments style, because the whole highlightling
thing is handled by the theme itself.

Customizing the theme
=====================

It's recommended to customize the theme when you use it, because even changing
the titles' font and links' color will give to your documentation an unique
feel.

The easiest way to customize it is to create a theme which inherits from the
main one, and changing the options::

   [theme]
   inherit = pietroalbini

   [options]
   accent_color = #004dc2
   night_accent_color = #5c9dff

   titles_font = DejaVu

Then you can put in your stylesheet other customizations you want to apply, and
the code to import the font you want to use for the titles.

Available theme options
=======================

Here there is a list of all the available theme options:

* **accent_color**: the main color used by the theme, for links and keywords in
  the code boxes
* **night_accent_color**: the same as *accent_color*, but used in the night
  (dark) mode
* **titles_font**: name of the font used in titles and headings

.. _Sphinx: http://sphinx-doc.org/