semvec/pypi-packages huggingface dataset:
jsonschema-lint 0.1.0
Linter for JSON Schema instances.
Requires Python: >=3.8,<4.0

# jsonschema-lint

Linter for JSON Schema instances.

## Installation

This project is not currently packaged and so must be installed manually.

Clone the project with the following command:
```
git clone https://github.com/jacksmith15/jsonschema-lint.git
```

## Usage

The linter is invoked on the command line:

```
$ jsonschema-lint
```

### Selecting instances

By default, the linter will attempt to lint every file matching extension under the currect directory. This means every `.json` file, plus every `.yaml`/`.yml` file if [PyYAML] is installed. A file will only be linted if a matching schema can be detected (see [below](#-selecting-schemas)).

You can override this behaviour by passing arguments to the linter, e.g.

```
$ jsonschema-lint **/*.avsc
```

### Schema resolution

There are three ways schemas can be selected for a given instance. In order of priority:

1. If provided, the `--schema` option will be used to validate all target instances.
1. A matching rule in a `.jsonschema-lint` file, in the instance directory or its parents (see below).
1. If the `--schema-store` flag is provided, then matching rules from [Schema Store](https://www.schemastore.org/json/) will be used.


#### `.jsonschema-lint` files

`.jsonschema-lint` files follow similar logic to `.gitignore` and [Github `CODEOWNERS` files](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners), in that they apply to all files under their directory tree.

Each line in a `.jsonschema-lint` file is a rule, matching a filepath pattern to a particular schema. For example:

```
**/.circleci/config.yml  https://json.schemastore.org/circleciconfig.json  yaml
```

There are three parts to each rule, separated by whitespace. These are:

- the pattern/glob, in this case matching any files named `config.yml` in a directory named `.circleci`
- the location of the schema. This can be a remote URL, or a path on the local filesystem. If this is a relative path, it is resolved relative to the `.jsonschema-lint` file.
- (optional) the expected file format of any instances. If this is omitted, the linter will attempt to detect the correct type from the file extension. If it cannot be detected, both will be attempted.


## Development

Install dependencies:

```shell
pyenv shell 3.9.4  # Or other 3.9.x
pre-commit install  # Configure commit hooks
poetry install  # Install Python dependencies
```

Run tests:

```shell
poetry run inv verify
```

# License

This project is distributed under the MIT license.


[PyYAML]: https://pypi.org/project/PyYAML/
q26-alphatrading 0.1.1
A python package for trading
Requires Python: >=3.6

[1]: https://www.q26.io
[2]: https://www.q26.io/data/q26_backtest_system/doc/html/
[3]: https://github.com/LoannData/Q26_QuanTester/wiki/Hands-on-:-A-simple-backtest

## Q26_QuanTester

Q26 Backtest System is a financial investment simulation tool dedicated for algorithmic traders developped in Python 3. 

### Main features : 
- Python based : very simple configuration file & strategies design model 
- High personnalisation and very wide way of use of the tool 
- Environment free of any development bias : 
  - No access to future data during the simulation   
- Pre-Backtest data preparation : 
  - Missing data filling models 
  - Possibility to resample data to any timeframe 
  - Multiple asset synchronization 
- High realism portfolio : 
  - Leverage, margin constraints, other security constraints 
  - High precision symbols characteristics : lot size, minimum lot size, open/close/off trading hours, fees ... 
- Fully personnalisable strategies & outputs 
- Parallelisable backtest, performance optimisation & MC approach 

And a lot more features ... 

And a lot of new features soon ! 

To get more informations about the Backtest System and the other products of Q26, you can visit our web site by clicking [here][1]. Get access to the detailled documentation [here][2] 

### Getting the Q26 Backtest System 

Download the code by cloning the git repository using 
```
git clone https://github.com/LoannData/Q26_QuanTester.git
```

or install the latest stable version using
``` 
pip install q26-quanTester
```

### Hands-on 

[Here][3] you can find a tutorial which shows how to hands-on the Q26 Backtest system
ci-plumber 1.4.2
Plumb together different CI/CD services
Requires Python: >=3.9,<4.0

# CI Plumber

[![CodeFactor](https://www.codefactor.io/repository/github/pbexe/ci-plumber/badge)](https://www.codefactor.io/repository/github/pbexe/ci-plumber) ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/ci-plumber) ![PyPI](https://img.shields.io/pypi/v/ci-plumber) ![PyPI - Downloads](https://img.shields.io/pypi/dm/ci-plumber) [![python-app](https://github.com/pbexe/ci-plumber/actions/workflows/python-app.yml/badge.svg)](https://github.com/pbexe/ci-plumber/actions/workflows/python-app.yml) [![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.5545987.svg)](https://doi.org/10.5281/zenodo.5545987)


A tool to create and configure all of the stages of a CI/CD pipeline.

Current integrations:
- Gitlab
- Gitlab pipelines
- Azure App Service
- Azure Image Registry
- Azure MariaDB
- Openshift
- Openshift MariaDB

Full documentation is available [here](https://milesbudden.com/ci-plumber/).

## Installation

```sh
pip install ci-plumber[all]
```

### Requirements

- `oc` CLI tool
- `az` CLI tool

## Usage

### GitLab
```sh
# Initialise the project
ci-plumber gitlab init
```

### OpenShift

```sh
# Deploy from the current docker registry to OpenShift
ci-plumber openshift deploy

# Create a new DB and store the credentials in maria.env
ci-plumber openshift create-db
```

### Azure

```sh
# Log in to Azure
ci-plumber azure login

# List your Azure subscriptions
ci-plumber azure list-subscriptions

# Set the subscription to use
ci-plumber azure set-default-subscription

# Create a docker registry
ci-plumber azure create-registry

# Trigger a build and push
git add .
git commit -m "Added Azure CI file"
git tag -a v1.0.0 -m "Version 1.0.0"
git push --follow-tags

# Deploy to Azure
ci-plumber azure create-app

# Create a database and store the credentials in maria.env
ci-plumber azure create-db
```

## Developing

### Installation
```sh
# Install dependencies
$ poetry install
$ poetry shell

# Install git hooks
$ pre-commit install
$ pre-commit autoupdate
$ pre-commit run --all-files

# Symlink the plugins back to the main project
$ ln -s ./plugins/example/ci_plumber_example/ ./ci_plumber_example
$ ln -s ./plugins/gitlab/ci_plumber_gitlab/ ./ci_plumber_gitlab
$ ln -s ./plugins/openshift/ci_plumber_openshift/ ./ci_plumber_openshift
$ ln -s ./plugins/azure/ci_plumber_azure/ ./ci_plumber_azure
```

### Features

- Runs checks on commit
    - Flake8
    - Black
    - pre-commit-hooks checks
    - mypy
    - isort
- Installable as a script