IDBio SDK em pacote Python (pronto para Django)
Este diretório agora possui um pacote instalável para usar o leitor no backend.
Estrutura
- src/idbio_sdk/cidbio.py: wrapper ctypes da DLL
- src/idbio_sdk/init.py: exports do pacote
- pyproject.toml: metadados para instalação via pip
- examples/django_app/: exemplo de serviço + views + urls para API
Instalação local do pacote
No diretório python:
- python -m pip install -U pip
- python -m pip install -e .
Teste rápido:
- python example.py
Uso no Django
Importe no backend:
- from idbio_sdk import CIDBio, RetCode
Arquivos de exemplo:
- examples/django_app/idbio_service.py
- examples/django_app/views.py
- examples/django_app/urls.py
No seu projeto Django, inclua as rotas do exemplo no urls.py principal.
Arquitetura recomendada (importante)
- O navegador (frontend web) normalmente nao acessa diretamente a DLL USB.
- Quem deve acessar o leitor e a DLL e o backend Django rodando na maquina que possui o USB conectado.
- O frontend chama endpoints HTTP do backend (por exemplo: /idbio/device-info/ e /idbio/capture/).
Se o frontend estiver em outra maquina, use um agente local (servico Windows) perto do leitor e faca o Django conversar com ele por HTTP seguro.
API implementada no wrapper
- Ciclo do dispositivo: Init, Terminate, SetSerialCommPort
- Captura: CaptureImage, CaptureImageAndTemplate, CheckFingerprint, CancelCapture
- Cadastro e identificacao: CaptureAndEnroll, CaptureAndIdentify, CaptureAndMatch
- Templates: ExtractTemplateFromImage, MergeTemplates, MatchTemplates, MatchTemplateByID
- Armazenamento: GetTemplateIDs, GetTemplate, SaveTemplate, DeleteTemplate, DeleteAllTemplates
- Configuracao e dispositivo: SetParameter, GetParameter, GetDeviceInfo, UpdateFirmware
- Erros: GetErrorMessage
Observacoes
- O SDK retorna ponteiros alocados em C. O wrapper copia o conteudo e libera memoria com as funcoes da DLL.
- Os retornos seguem o enum RetCode.
Metadata
Release files for idbio-sdk 0.1.0
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 |
|---|---|---|---|---|
| idbio_sdk-0.1.0.tar.gz | 530.7 kB | Without provenance | Details for idbio_sdk-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| idbio_sdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for idbio_sdk-0.1.0-py3-none-any.whl |
Total release size: 1.1 MB
Release files / idbio_sdk-0.1.0.tar.gz
| Download URL | idbio_sdk-0.1.0.tar.gz |
|---|---|
| Size | 530.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37d49605d95d1a998d7432da8bc1d32c80c4d78471d48f9e59fb1d8de58ed224
|
|
BLAKE2b-256 checksum How to use checksums |
29faad1d0c18f106145763551532c53c63eba3929da9978870d5a515b42a73d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.10
|
Release files / idbio_sdk-0.1.0-py3-none-any.whl
| Download URL | idbio_sdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 532.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1d097f5a847419235df7af123ccd436a1ef65d679106523f7301cf8c7084de5
|
|
BLAKE2b-256 checksum How to use checksums |
ecb65e6ed1b12c87cae5fe62631d7842197f263a12cb7c225799bc9217729cbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.10
|
Security for idbio-sdk 0.1.0
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.