semvec/pypi-packages huggingface dataset:
picnic-python 0.2.0
Picnic API Python client library
License: MIT
Keywords: development picnic.sh

Official Picnic API client library for Python
=============================================

A Python library for Picnic's API. Python 2.7.9 and 3.4.3 (and above) are supported.

Setup
-----

You can install this package—and its one dependency, ``requests``—by doing::

    pip install picnic-python

or::

    easy_install picnic-python

Obtaining a Picnic API Key
--------------------------

Sign up for an API key at https://picnic.sh/api.

Using the Picnic API
--------------------

Documentation for the API can be found at https://picnic.sh/api.

Using this client library
-------------------------

For a quick demonstration of the available methods, please see `example.py`_.

.. _example.py: example.py

list_websites()
^^^^^^^^^^^^^^^

Returns a list of ``Website`` s that you own.

get_website(*domain_name*)
^^^^^^^^^^^^^^^^^^^^^^^^^^

Returns a ``Website`` referred to by the given *domain_name*.

get_price(*domain_name*)
^^^^^^^^^^^^^^^^^^^^^^^^

Returns a ``DomainStatus`` for the given *domain_name*.

create_website(*domain_name*, *html*)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Creates a website with the given *html* content at the given *domain_name*, if available. If successful, returns a ``Website``.

Website.update_content(*html*)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Overwrites the ``Website``'s content with the given *html*.
pyci 0.0.4
Continuous integration server for Github and MediaWiki.
License: MIT

Py-CI
=====

Generic continuous integration server for interfacing with github and
publishing results to a Media Wiki. The basic idea is that continuous
integration just requires three things:

-  A repo to monitor for changes.
-  Unit tests to run.
-  A place to publish the results of the tests.

``Py-CI`` interfaces with github using the
`pygithub <https://github.com/PyGithub/PyGithub>`__ API wrapper for
interfacing with github's API. It monitors the pull requests for a set
of repos. When a new or untested pull request is found:

-  Create a local copy of the repo; merge the proposed changes from the
   pull request into a working branch.
-  Run all the unit tests specified in the ``repo.xml`` configuration
   file.
-  Post the results of running the unit tets to a media wiki.

Quickstart
----------

If you already have a
`virtualenv <https://virtualenv.pypa.io/en/latest/>`__ installed as well
as
`virtualenvwrapper <https://virtualenvwrapper.readthedocs.org/en/latest/>`__,
skip this next code block. However, be sure to add the ``VENV`` variable
to the `global configuration
file <https://github.com/rosenbrockc/ci/wiki>`__.

::

    pip install virtualenv
    pip install virtualenvwrapper
    mkvirtualenv ci

Next, copy the
```global.xml`` <https://github.com/rosenbrockc/ci/wiki>`__ file and put
it somewhere on you local disk (say ``~/.ci.global.xml``). Be sure to
**edit the values**. Then:

::

    export PYCI_XML="~/.ci.global.xml"
    workon ci
    pip install py-ci
    sudo ci.py -setup

If you don't see any errors, your server is ready to have repositories
installed. This configures the server cron to run *every minute*. Use
``-cronfreq [int minutes]`` to change that frequency (see `cron
settings <https://github.com/rosenbrockc/ci/wiki/Cron-Implementation>`__
for details). You don't need to use ``sudo`` for anything *except*
setting the server up initially (or uninstalling it later with the
``-rollback`` switch). Next, create a
```repo.xml`` <https://github.com/rosenbrockc/ci/wiki/Repository-Level-Settings>`__
file for repository you want to monitor. Suppose it exists at
``~/repos/myrepo/ci.xml``, then:

::

    ci.py -install ~/repos/myrepo/ci.xml

Your repository will now be monitored for new pull requests forever
untill you either ``-uninstall`` the ``repo.xml`` file *or* you
``-disable`` the CI server to temporarily suspend all requests. To
understand the behavior of the CI server, read through the `repository
level
settings <https://github.com/rosenbrockc/ci/wiki/Repository-Level-Settings>`__
page.

**IMPORTANT:** if your unit tests require environment variables to be
set, they need to be added to a file called ``~/.cron_profile`` that
will be loaded by the CI server whenever the cron is run. See `cron
environment
variables <https://github.com/rosenbrockc/ci/wiki/Environment-Variables-for-Unit-Tests>`__
for more details.
binstarsolver 0.1.3
Estimate physical quantities of a binary star system from observed quantities.
License: MIT
Keywords: astronomy astrophysics binary stars observing

binstarsolver
=============

.. image:: https://zenodo.org/badge/4765/ccd-utexas/binstarsolver.svg   
        :target: http://dx.doi.org/10.5281/zenodo.16983

Overview
--------

The purpose of this project is to estimate physical quantities of an eclipsing, spectroscopic binary star system using observed quantities from photometry and spectroscopy.
The estimated physical quantities serve as input to a more complete numerical model such as that of Wilson-Devinney, c.f. chapter 7 of [1]_.
The model used in this project is a simple, spherical detached binary star model with no orbital eccentricity and no limb darkening.
The model is from chapter 7 of [2]_ and chapter 7 of [3]_.

Input observed quantities
-------------------------

* Relative times of begin/end ingress/egress and mid-eclipse.
* Orbital period.
* Light levels during occultation (primary eclipse), transit (secondary eclipse), and outside of eclipse.
* Stellar radial velocities.

Output estimated physical quantities
------------------------------------

* Orbital inclination angle.
* Orbital radii.
* Stellar masses.
* Stellar radii.
* Ratio of stellar radiative fluxes.
* Ratio of stellar effective temperatures.
* Ratio of stellar luminosites.

Examples and Q&A forum
----------------------

* For explanations of examples, please see the `binstarsolver GitHub wiki <https://github.com/ccd-utexas/binstarsolver/wiki>`_.
* For questions and discussion, please see the `binstarsolver Google group <https://groups.google.com/forum/#!forum/binstarsolver>`_.
* Got a second for a `user survey <https://docs.google.com/forms/d/1vneANTMMaOdQSRvIm2OJYItgaTTbp4f9EM8ImKqwD-g/viewform>`_? I'd love your feedback! Thank you for being part of open science. (All survey responses are anonymous.)

Citations
---------

* If this code is useful to your academic research, please consider citing it by including this DOI link: http://dx.doi.org/10.5281/zenodo.16983

Recent changes
--------------

* [v0.1.3] - 20150420T180000
   - Created Google group, DOI for citations, CHANGELOG.rst, IPython Notebook examples.
   - Fixed special cases where solver for inclination did not converge.
* [v0.1.2] - 20150123T172000
   - Initial release to PyPI.

References
----------

.. [1] `Kallrath and Milone, 2007, Eclipsing Binary Stars: Modeling and Analysis <https://books.google.com/books?id=CrXBnZFdjXgC>`_
.. [2] `Budding, 2007, Introduction to Astronomical Photometry <https://books.google.com/books?id=g_K3-bQ8lTUC>`_
.. [3] `Carroll and Ostlie, 2007, An Introduction to Modern Astrophysics <https://books.google.com/books?id=M8wPAQAAMAAJ>`_
tgext.langdomain 0.0.1
TurboGears2 extension for detecting user language from the domain
License: MIT
Keywords: turbogears2.extension

About tgext.langdomain
----------------------

tgext.langdomain is a TurboGears2 extension that supports detecting the user
language from the domain it is connecting from.

Installing
----------

tgext.langdomain can be installed from pypi::

    pip install tgext.langdomain

should just work for most of the users.

Enabling
--------

To enable tgext.langdomain put inside your application
``config/app_cfg.py`` the following::

    import tgext.langdomain
    tgext.langdomain.plugme(base_config)

or you can use ``tgext.pluggable`` when available::

    from tgext.pluggable import plug
    plug(base_config, 'tgext.langdomain')

Options
-------

langdomain will force the language of the current request based on:
**Top Level Domain**, **SubDomain** and **param** unless there is
already a language stored into the session.

**By default none of those behaviours is enabled**

When plugging langdomain the following options to turn on behaviours are available:

    *param* -> Name of the GET param used to force language, ``True`` means ``lang``.

    *tld* -> Dict of *tld* that map to a language

        EXAMPLE::

             plug(app_cfg, 'tgext.langdomain',
                  tld={
                    'com': 'en',
                    'it': 'it'
             })

    *subdomain* -> Dict of subdomains that map to a language

        EXAMPLE::

             plug(app_cfg, 'tgext.langdomain',
                  subdomain={
                    'en': 'en',
                    'it': 'it'
             })

When requests are performed like **it.server.net** it will lookup **it** inside
the ``subdomain`` dictionary and **net** inside the ``tld`` dictionary.