semvec/pypi-packages huggingface dataset:
coinmarketcap-web-api 0.0.12
coinmarketcap_web_api
Requires Python: >=3.4

# py_coinmarketcap_web_api

![PyPI - package version](https://img.shields.io/pypi/v/py_coinmarketcap_web_api?logo=pypi&style=flat-square)
![PyPI - license](https://img.shields.io/pypi/l/py_coinmarketcap_web_api?label=package%20license&style=flat-square)
![PyPI - python version](https://img.shields.io/pypi/pyversions/py_coinmarketcap_web_api?logo=pypi&style=flat-square)
![PyPI - downloads](https://img.shields.io/pypi/dm/py_coinmarketcap_web_api?logo=pypi&style=flat-square)

![GitHub - last commit](https://img.shields.io/github/last-commit/kkristof200/py_coinmarketcap_web_api?style=flat-square)
![GitHub - commit activity](https://img.shields.io/github/commit-activity/m/kkristof200/py_coinmarketcap_web_api?style=flat-square)

![GitHub - code size in bytes](https://img.shields.io/github/languages/code-size/kkristof200/py_coinmarketcap_web_api?style=flat-square)
![GitHub - repo size](https://img.shields.io/github/repo-size/kkristof200/py_coinmarketcap_web_api?style=flat-square)
![GitHub - lines of code](https://img.shields.io/tokei/lines/github/kkristof200/py_coinmarketcap_web_api?style=flat-square)

![GitHub - license](https://img.shields.io/github/license/kkristof200/py_coinmarketcap_web_api?label=repo%20license&style=flat-square)

## Description



## Install

~~~~bash
pip install py_coinmarketcap_web_api
# or
pip3 install py_coinmarketcap_web_api
~~~~

## Usage

~~~~python
from coinmarketcap_web_api import CoinMarketCap

cmc = CoinMarketCap()

cmc.get_token(cmc.get_recent_tokens()[0].slug).jsonprint()

# for token in cmc.get_recent_tokens():
#     token.jsonprint()
~~~~

## Dependencies

[jsoncodable](https://pypi.org/project/jsoncodable), [ksimpleapi](https://pypi.org/project/ksimpleapi), [noraise](https://pypi.org/project/noraise), [requests](https://pypi.org/project/requests)
flask-scaffolding 0.0.29
Flask Scaffolding with buiiltin Authentication & Authorization
Requires Python: >=3.6

# Flask-Scaffolding-Base
- Flask Scaffolding with builtin Authentication & Authorization
- Installation : 
```
pip install flask-scaffolding
```
- Run to create a new flask app with the given name and destination path.
```
python -m scaffold.web <YOUR_APP_NAME> <path/to/destination>
```
- Add your custom model into `<YOUR_APP_NAME>/app/models/`, 
- Run to add a new screen UI on created app above,
```
python -m scaffold.ui <MODEL_NAME> <path/to/model/file/location>
```
viridicle 0.1.1
Fast stochastic ecological simulations on graphs in Python and numpy
Requires Python: >=3.6

## What is Viridicle? <img align="right" src="example.gif">

Viridicle is a library for simulating stochastic graphical ecological models. It implements the continuous time models described in Section 6 of [Durrett and Levin 1994](https://www.researchgate.net/publication/230693004_Stochastic_Spatial_Models_A_User's_Guide_to_Ecological_Applications). The library is written in C for speed, but has a Python API for ease of use. It supports well-mixed systems, multi-dimensional periodic lattices, and arbitrary graphs, with up to 256 species, and is substantially faster than comparable software written in Python alone.

Viridicle models an ecological system as a graph, where each vertex denotes a discrete site - an island, an oasis, a point on a Petri dish, etc. Each site is small enough that we can model its state by assigning it a single number specifying which species is occupying it. Traditionally, 0 denotes an unoccupied site, but neither the mathematics nor the code require this.

The system changes over time as a [continuous-time Markov chain](https://en.wikipedia.org/wiki/Continuous-time_Markov_chain), where each directed edge in the system is a [Poisson point process](https://en.wikipedia.org/wiki/Poisson_point_process). That is, at any given moment, for every edge in the system, the time until the edge's vertices change to state <img src="https://render.githubusercontent.com/render/math?math=(s_1,s_2)"> is exponentially distributed with some rate that depends on the state of the system. The model is implemented using the [Gillespie algorithm](https://en.wikipedia.org/wiki/Gillespie_algorithm). For further details, consult the [documentation](https://www.theorem-engine.org/viridicle/index.html).

## Installation

To install Viridicle from the PyPi repo, run:

```
pip install viridicle
```

If you want to compile from source yourself, first make sure that you have gcc installed, along with Python, including its development headers. Then, run:

```
git clone https://github.com/TheoremEngine/viridicle.git
cd viridicle
python3 setup.py install
```
finthermos 0.0.1
Infrastructure for Finance

# Thermos

[![CI release check](https://github.com/tbonza/thermos/actions/workflows/main.yml/badge.svg)](https://github.com/tbonza/thermos/actions/workflows/main.yml)

Thermos is infrastructure for financial markets.

## Getting started

Build and test using Cmake.

## Thermos Philosophy

A thermos is a reliable container to keep your beverages warm. I use
mine almost daily to enjoy tea such as Yerba Mate. My thermos feels 
reliable to me because of the simple construction and use of durable 
materials like thick stainless steel. The thermos does one thing well 
which is similar to the Unix Philosophy.

Basics of the Unix philosophy, documented by Doug Mcllroy in the 
Bell System Technical Journal from 1978, described by [Eric S. 
Raymond who wrote The Art of Unix Programming](http://www.catb.org/~esr/writings/taoup/), "is bottom-up, not top down". Mcllroy 78 had this
to say at the time:

* Make each program do one thing well. To do a new job, 
  build afresh rather than complicate old programs by adding 
  new features.
* Expect the output of every program to become the input to another, 
  as yet unknown, program. Don't clutter output with extraneous 
  information. Avoid stringently columnar or binary input formats. 
  Don't insist on interactive input.
* Design and build software, even operating systems, to be tried 
  early, ideally within weeks. Don't hesitate to throw away the 
  clumsy parts and rebuild them.
* Use tools in preference to unskilled help to lighten a programming task, 
  even if you have to detour to build the tools and expect to throw some 
  of them out after you've finished using them.

Drawing inspiration from both my thermos and basics of the Unix Philosophy,
Thermos is intended to create a similar feeling for me in regards to 
infrastructure for financial markets.