semvec/pypi-packages huggingface dataset:
ripe 0.0.4
remove & reinstall python packages in one command
License: MIT

# ripe  [![Build Status](https://travis-ci.org/shaunvxc/ripe.svg?branch=master)](https://travis-ci.org/shaunvxc/ripe) [![PyPI version](https://badge.fury.io/py/ripe.svg)](https://badge.fury.io/py/ripe) [![forthebadge](https://img.shields.io/badge/warning-NSFW-orange.svg)](http://forthebadge.com)
An unnecessary micro-optimization for those who (like me) spend too much time using `--force-reinstall` or `pip uninstall`/`install` while testing every little incremental change to their packages. 

## Why?
If you find yourself in a workflow where you are continuously reinstalling local copies of your packages to test out changes, you might find `ripe` to be a useful little hack.

While `pip` itself offers equivalent functionality with its `--force-reinstall` flag, `ripe` will accomplish the same thing in fewer keystrokes.  

## Usage

- Run from the root-level of a package to uninstall the currently installed version, and reinstall using your local changes:

    `$ ripe` 

- You can also point ripe to the package you wish to reinstall with your local changes:

    `$ ripe packagename`
 
- For more complicated paths:

    `$ ripe /path/to/local/package`

In all cases, `ripe` will automatically pass `y` to the `Proceed (y/n)` prompt for uninstalling.

***Note*** `ripe` must either be run from or pointed to a `pip-installable` location (it checks for `setup.py`. If it is run from elsewhere, it will tell you as much before exiting) 

## Installation

`$ pip install ripe`


#### Disclaimer
This is a little tool that uses `os.system()` to `pip uninstall` and `pip install` the local copy of your package onto your system (or current virtual environment).  As such this package should **only** be used locally and properly.
gdo 0.1.2
Concurrent execution library
License: MIT

.. image:: https://travis-ci.org/uluyol/gdo.svg?branch=master
    :target: https://travis-ci.org/uluyol/gdo

.. image:: https://coveralls.io/repos/github/uluyol/gdo/badge.svg?branch=master
    :target: https://coveralls.io/github/uluyol/gdo?branch=master
SSKJpy 0.1.1
A Slovenian dictionary API
License: MIT
Keywords: python

===========
SSKJpy
===========

A Slovenian dictionary API written in python

Uses http://bos.zrc-sazu.si/sskj.html (official SSKJ) website.

**Simple examples:**

.. code:: python

    from sskjpy import SskjParser
    
    keyword = "test"
    search = SskjParser(keyword)

Now we can do

.. code:: python

    print(search.shortsum())
    "postopek za ugotavljanje določenih lastnosti, sposobnosti, znanja koga, preizkus"

    print(search.result())
    "tést  -a m (ẹ̑) 1. postopek za ugotavljanje določenih lastnosti, sposobnosti, znanja koga, preizkus: opraviti test; s testom ugotavljati sposobnosti; objektivnost, veljavnost, zanesljivost"

More examples can be found at `GitHub <https://github.com/DefaltSimon/SSKJpy/wiki>`_
metamod 0.0.2
ORM that uses __slots__ (for memory saving), plain DBAPI2 connections (to not break threading) and assumes the user knows SQL
License: MIT

overview
--------

metamod stands for 'metaclass models'.

* lightweight ORM (about 200 lines)
* uses python's `__slots__` so instances are lightweight and classes are self-documenting

vs other ORMs
-------------

The goal here is to be a thin layer on SQL. We want to wrap simple, well-understood and often-repeated actions like:

* create table
* insert
* simple select statements (where field=value)

Database writes are emitted as raw SQL that you can pass to a cursor. Database reads operate on a cursor (but *not* on a connection; you manage your connections yourself).

We don't want to:

* generate complex SQL statements, especially for joins
* provide any type conversions (adapt / mogrify); we'll trust psycopg2 or pymysql for that
* normalize behavior across different DBs
* hide connections & pooling behind classes

See github page for examples.