semvec/pypi-packages huggingface dataset:
setuptools-scm-azure-pipelines 0.1.0
'setuptools_scm plugin that versions `post` packages with Azure Pipelines BUILD_BUILDID number.'
License: MIT
Requires Python: >=3.6

# `setuptools_scm_azure_pipelines`

## Description

A stupidly simple [`setuptools_scm`](https://github.com/pypa/setuptools_scm) plugin that generates
 [PEP-440 post-releases](https://www.python.org/dev/peps/pep-0440/#toc-entry-8) packages versions prefixed
 with the Azure Pipelines `${BUILD_BUILDID}` for builds that happen on non-tagged git commits.

`BUILD_BUILID`, or rather `$(Build.BuildId)` in the Azure Pipeline lingo, is the variable that is set
by Azure Pipelines when a build is running.

When this variable is present and you are using this tool, your package's version will be:
- `{tag}`, e.g. `1.2.3` when you are building on a tag ("exact version"),
- `{tag}.post{BUILD_BUILDID}`, e.g. `1.2.3.post12345` when you are building an intermediate version ("on-commit"),

This allows your fellow developpers to get the "latest" version of a package, no matter what.

You might not want that to happen everytime, though. In that case, don't forget to pin you dependencies correctly using one of:
-   [`pip-tools`](https://github.com/jazzband/pip-tools)
-   [`Pipenv`](https://github.com/pypa/pipenv)
-   [`Poetry`](https://python-poetry.org/)

## Usage

### Usage in `pyproject.toml`

Set it up in `pyproject.toml` `[build-system]` section like this:

```toml
[build-system]
requires = ["setuptools>=45", "wheel", "setuptools_scm>=6.2", "setuptools_scm_azure_pipelines>=1.0"]

[tool.setuptools_scm]
local_scheme = "no-local-version"
version_scheme = "post-release-azure-build-id"
```
esp32-test-stubs 0.1.2
Sample project for PEP-561 distribution testing
License: MIT
Requires Python: >=3.8,<4.0

esp32-test-stubs
================

Sample project for test [PEP-561][1]

Notice: It is only "proof-of-concept" of [PEP-561][1] package so **not for production use**, 
package can be deleted in the future. 

## Installation

```shell 
pip3 install esp32-test-stubs
```

## Script

```python
import machine
machine.freq()

import esp32
esp32.NVS()
esp32.wake_on_ext0("Test")

from esp.sub_pkg import sub_pkg_fun
sub_pkg_fun()

from esp32.sub_pkg import sub_pkg_function
sub_pkg_function()

import uuid

# Points to stdlib
uuid.uuid4()

# Points to stub (mean partial stub, so extent stdlib)
# see uuid-stubs and py.typed
uuid.uuid6()

import upip
upip.cleanup()
```

## Stubs possible locations

- project root `*.pyi` files
- `<package>-stubs` with `__init__.pyi` see [PEP-561](https://www.python.org/dev/peps/pep-0561)
- `<package>-stubs/<sub_package>.pyi` see [stub-only-packages](https://www.python.org/dev/peps/pep-0561/#stub-only-packages)
- custom folder like `src`, marked as `package = [{ include = "*.pyi" , from = "src"}]`,
  under hood all `*.pyi` will be moved into package root during package build.  
  CONS: **Not recommended** as custom folder does not recognize as stub source before stub package will pack properly. 
  Also in `*.tar.gz` stubs not moved properly, so it led to potential errors during stub recognition   

Note all of these variants should be explicitly marked in `pyproject.toml` in `Poetry` see `package` section

## Poetry commands

- Prepare
  ```shell 
  poetry config repositories.testpypi https://test.pypi.org/legacy/
  poetry config pypi-token.testpypi <TOKEN>

  poetry config repositories.pypi https://upload.pypi.org/legacy/
  poetry config pypi-token.pypi <TOKEN>
  ```

- Publish
  ```shell 
  poetry publish --build -r testpypi
  poetry publish --build -r pypi
  ```

## Links

- [PEP-561](https://www.python.org/dev/peps/pep-0561)
- [Real world stubs example (Numpy)](https://github.com/numpy/numpy-stubs)
- [Poetry project examples](https://github.com/python-poetry/poetry/tree/master/tests/masonry/builders/fixtures/pep_561_stub_only)

#### Footnotes
[1]: https://www.python.org/dev/peps/pep-0561
hermes-se2021 1.0.1
A small tool for data collection and processing for SE2021 HSE SPb course
License: MIT
Requires Python: >=3.8,<4.0

# Hermes

## Project description

This project's implementation is a part of SE course in Higher School of Economics. 

Hermes is a platform for collecting data from hospitals and clinics and using this data for training ML models. 

Project presentation is available [here](https://docs.google.com/presentation/d/1H6xPu8CtyLfUVIbjr5ZoOuYPqUBmz5ivMpN5mHBR6Hw/edit?usp=sharing)

The project is currently in an initial state.

## Instructions

### Install

`pip install hermes-se2021`

### Build from source

```bash
git clone git@github.com:MariaChizhova/SE_2021.git
cd SE_2021

python3 -m pip install poetry
poetry install
```

#### Install from source
```bash
poetry build
python3 -m pip install "$(find dist -name "*.whl" -print -quit)"
```

### Usage

#### Run web application:

```bash
poetry run uvicorn hermes.endpoints:app --reload
```

#### Using as a library
```python
import hermes
import hermes.stroke_regressor
```

### Tests

```
poetry run ./tests.sh all
```

## Roadmap

The roadmap of the project is available [here](https://github.com/MariaChizhova/SE_2021/projects/3)

## CHANGELOG

The changelog of the project is available [here](https://github.com/MariaChizhova/SE_2021/blob/hw_04/CHANGELOG.md)

## Acknowledgements

Thanks to our teachers (Vladislav Tankov, Timofey Bryksin) for created this task!

## Contributors

Maria Chizhova: @MariaChizhova

Anna Potryasaeva: @annapotr

Jura Khudyakov: @23jura23 

## Contributing

Pull requests are welcome!

### Additional instructions

#### Develop in venv with all dependencies:

After executing `poetry install`:

- Use `poetry shell` to launch a shell with all dependencies
- For usage with PyCharm one can use virtual environment from `~/.cache/pypoetry/virtualenvs` 

#### Deploying to PyPi repository

```bash
poetry publish
```

## License

[MIT](https://choosealicense.com/licenses/mit/)