semvec/pypi-packages huggingface dataset:
joes-ntpdate 1.9.78
Joe's own ntpdate: set the date and time via NTP
License: MIT
Keywords: ntpdate,hwclock,time,clock,synchronize

.. image:: https://img.shields.io/travis/erikrose/joes-ntpdate.svg
    :alt: Travis Continous Integration
    :target: https://travis-ci.org/erikrose/joes-ntpdate/

.. image:: https://coveralls.io/repos/erikrose/joes-ntpdate/badge.png?branch=master
    :alt: Coveralls Code Coverage
    :target: https://coveralls.io/r/erikrose/joes-ntpdate?branch=master

.. image:: https://img.shields.io/pypi/v/joes-ntpdate.svg
    :alt: Latest Version
    :target: https://pypi.python.org/pypi/joes-ntpdate

.. image:: https://pypip.in/license/joes-ntpdate/badge.svg
    :alt: License
    :target: http://opensource.org/licenses/MIT

.. image:: https://img.shields.io/pypi/dm/joes-ntpdate.svg
    :alt: Downloads
    :target: https://pypi.python.org/pypi/joes-ntpdate


Joe's Own ntpdate
=================

Set the date and time via NTP.

Assumes bsd or gnu date(1) and gnu hwclock(8) if applicable.

This implementation doesn't mess around.  It requires root privileges,
and sets the operating system and hardware clock to whatever value
is found by the given ntp server.

::

        usage: joes-ntpdate [-h] [--set-system] [--set-hwclock] [--retries [N]]
                            [--backoff-factor N]
                            [ntp_host]

        Joe's own ntpdate: report or set clock by remote ntp host.

        positional arguments:
          ntp_host            remote ntp host to synchronize clock with. (default:
                              pool.ntp.org)

        optional arguments:
          -h, --help          show this help message and exit
          --set-system        Set system clock to remote time. (default: False)
          --set-hwclock       additionally, set hardware clock. May do nothing on
                              platforms without hwclock(8) (default: False)
          --retries [N]       retry on failure up to N times. (default: 30)
          --backoff-factor N  retry backoff each step, sleep for {{<backoff-factor> *
                              <retry-step>}} (default: 2.0)

        Assumes bsd or gnu date(1) and gnu hwclock(8) if applicable.

This package uses `ntplib <https://pypi.python.org/pypi/ntplib/>`_
ciex 0.1.1a0
A simple, lightweight and modular CI system
License: MIT

ciex (alpha)
=========
a simple, lightweight and probably dumb CI system, written in Python.

**To extend it**, write your own python `ci workers` modules, then define them in the daemon's configuration file.

**An example** scenario would be to install the `ciex daemons` on multipe machines, then trigger the checkout command or build, upgrade, etc from another machine, say after you're pushing new code to the master branch.

# Quickstart
 Note: You need [nanomsg](https://github.com/nanomsg/nanomsg) installed on your system.

```shell
$ pip install ciex
$ ciexd --config /path/to/config/ciex.config
$ ciextl ping
pong
```

# Installation
If you have have [nanomsg](https://github.com/nanomsg/nanomsg) installed on your system, the installation should be pretty easy.

**Requirements**

* [nanomsg](https://github.com/nanomsg/nanomsg) - requirement for nanoservice
* [nanoservice](https://github.com/walkr/nanoservice) - for interprocess comm.
* [oi](https://github.com/walkr/oi) - for command line interface


**Install options**

```shell
# Using pip
$ pip install ciex

# Or using the makefile
$ git clone git@github.com:walkr/ciex.git
$ cd ciex
$ make install
```


# High level overview

The system has two separate components:

1. A daemon process `ciexd`
2. A command line interface `ciexctl`


### 1. Daemon

The daemon is running continuously awaiting for commands.
When a command is received, it is tranformed into a task,
then it is placed onto the `new queue`. **CI Workers** take tasks
from the `new queue` and do their work. When the work associated
with that task is finished, the CI Worker will mark the task as
`success` OR `failure`, then it will send it back to the task router.

The daemon accepts a configuration file, where you can define the settings
for each of your apps, as different apps have different needs.

**Example config file**

```ini
[settings.app.my_app]
localpath = /apps/my_app
repo = git@github.com:walkr/test.git

worker_dirpath = /apps/myapp/ci
worker_modname = workers
worker_classname = CustomWorker
```

**Starting the daemon**

```shell
$ ciexd --config /etc/ciex.config  # optional --debug flag
```


### 2. Command line interface

The command line interface accepts commands and forwards them to the daemon

**Usage Example:**

```shell
$ ciextl ping
pong

$ ciexctl
ctl > list
['appname1', 'appname2']

ctl > status appname1
<Task app_name:appname1, command:checkout, status:TaskStatus.success>

ctl > upgrade appname1
Task triggered ...

ctl > status appname1
<Task app_name:appname, command:upgrade, status:TaskStatus.pending>

# While a task is running, you cannot fire up another task
ctl > upgrade appname1
Deny. Taks already running
```


That's it. Enjoy!

**MIT License**
digiglass 1.0.4
Search Digi-Key from your terminal
License: MIT

Digiglass
=========

*Search Digi-Key from your terminal*

Searching Digi-Key can be a pain. Here's a list of things I do every
time I search for an item:

-  Filter by "In Stock"
-  Filter by "Quantity Desired: 1"
-  Sort by price, ascending

Each of those actions takes a click and a couple seconds to load. I can
automate these tasks and do most of the work from the command line.

Usage
=====

-  Search for blue LEDs:
   ``digiglass blue led``
-  Search for 470-ohm resistors in the through-hole category:
   ``digiglass -c 'through hole resistor' 470 ohm``
-  Browse all resistor kits:
   ``digiglass --category 'resistor kit'``

``-c`` and ``--category`` are interchangeable. Category names support
fuzzy search - you can type part of the name and the proper category
will probably appear.

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

This is a Python 3 script, so use ``pip3`` to install:

::

    pip3 install digiglass

Filters
=======

Specify a filter to be used during a search like this:
``digiglass --filter some_new_filter``

You can customize the filters used by Digiglass by modifying
``~/.digiglass``. It's a YAML file that looks like this:

::

    filters:
        my_filter:
            in_stock: true
            lead_free: false
            rohs_compliant: false
            sort_by: '1000011'  # Unit price, USD, ascending
            min_quantity: 1
        pb_rohs:
            lead_free: true
            rohs_compliant: true

    settings:
        default_filter: my_filter

Valid options are:

-  ``in_stock``: Item must be in stock
-  ``lead_free``: Item must be lead free
-  ``rohs_compliant``: Item must be RoHS compliant
-  ``sort_by``: The column by which to sort results
-  ``min_quantity``: At least this many of this item must be available

Every field in a filter is optional.

``default_filter`` is used when no filter is specified.

Fields not specified in a requested filter use the default filter's
settings.

Troubleshooting
===============

Having issues? Try clearing the app's cache: ``digiglass --clear-cache``

Still having issues? Odds are Digi-Key changed their HTML format. They
probably broke the app's screen scraping. Let me know and I'll try and
fix it—or dig in yourself! Screen scraping is fun.

Contributions
=============

Bug reports, fixes, or features? Feel free to open an issue or pull
request any time. You can also tweet me at
[@mplewis](http://twitter.com/mplewis) or email me at matt@mplewis.com.

License
=======

Copyright (c) 2014 Matthew Lewis. Licensed under `the MIT
License <http://opensource.org/licenses/MIT>`__.