Run general rotines from clinic
# Installation
To install the latest stable version from PyPi:
$ pip install -U incolumepy.inventario-clinica
To install the latest development version directly from GitHub:
$ pip install -U git+https://gitlab.com/development-incolume/incolumepy.inventario_clinica.git'@develop
$ pip install -U git+https://gitlab.com/development-incolume/incolumepy.inventario_clinica.git'@master
# Testing
> bash runtests.sh
or
> $ tox
# Guia de contribuição
## Repositório de desenvolvimento Local
Configure o repositório de desenvolvimento local conforme o tutorial: https://brito.blog.incolume.com.br/2018/11/repositorio-pypi-local-com-devpi-server.html.
### Ativar o servidor pypi local
```devpi-server --stop && devpi-server --start && devpi use http://localhost:3141/root/```
## Regras para codigicação
1. Criar um novo **branch** para cada etapa de codificação.
1. Crie o branch sempre a partir do master
1. As **branches** terão finalidades específicas:
* Introduzir novas funcionalidades (**feature**)
* Corrigir comportamento inesperado (**bug**)
* Corrigir comportamento inesperado que compromete o funcionamento (**critical**)
* Alterar a forma, mantendo o comportamento (**refactor**)
1. O nome da **branch deve ser prefixado com o tipo de alteração que será realizada** : (feature, bug, critical ou refactor)
* exemplos via terminal:
- bug/issue#21:
```git co -b bug/issue#21 origin/master```
- critical/issue#13:
```git co -b critical/issue#13 origin/master```
- feature/issue#23:
```git co -b feature/issue#23 origin/master```
- refactor/issue#30:
```git co -b refactor/issue#30 origin/master```
* Detalhes sobre git via terminal:
- [Guia Rápido de comandos git (lado usuário)](http://brito.blog.incolume.com.br/2013/03/guia-rapido-de-comandos-git-lado-usuario.html)
## Outros Detalhes
- [wiki do projeto](https://gitlab.com/clinicaesteticabrito/inventario_clinica/wikis/home)
Metadata
Release files for incolumepy.clinica 2018.12.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| incolumepy.clinica-2018.12.1.tar.gz | 6.1 kB | Without provenance | Details for incolumepy.clinica-2018.12.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| incolumepy.clinica-2018.12.1-py3.7.egg | Legacy Egg format | - | - | Details for incolumepy.clinica-2018.12.1-py3.7.egg |
Total release size: 11.6 kB
Release files / incolumepy.clinica-2018.12.1.tar.gz
| Download URL | incolumepy.clinica-2018.12.1.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00eeac2a7bf817b2b70462c81fe101d94bbf344efa1825518dd5c900c830e6e1
|
|
BLAKE2b-256 checksum How to use checksums |
ba7d2c549627a1247bb43f5caf1150446971afdae4b0abe0f5039538b8473601
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Release files / incolumepy.clinica-2018.12.1-py3.7.egg
| Download URL | incolumepy.clinica-2018.12.1-py3.7.egg |
|---|---|
| Size | 5.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
47f754e02f6dfbbaaac49ece7c988863ce9d5abe494048a94b6296128d85db95
|
|
BLAKE2b-256 checksum How to use checksums |
749b9213dad24fdf85ac646ae8cd71790f244af839c0b27f491e6991ebcaf497
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Security for incolumepy.clinica 2018.12.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.