mftoolbox
Package created to support my MF2 project development.
Functions:
- encoding(): returns the proper encoding for handling config files with configparser. It's based on the based on the operating system:
- UTF-16 for Windows;
- UTF-8 for Mac.
Classes:
- Build: automatically controls build number based on changes made to the file;
- UltimaCotacaoDolar: gets the last available BRL/USD exchange rate from Brazilian's Central Bank;
- Proventos: works with dividends data;
- Timestamp: formats execution start time information
- self.str_yyyymmdd: now() formatted as YYYYMMDD
- str_hhmmss: now() formatted as HHMMSS
- dtt_timestamp: now() as timestamp
- dtt_now: now() as datetime
- CotacaoDolarData: gets USD/BRL exchange rate for a specific date
- Arguments:
- Date: string with date formatted as DD/MM/YYYY
- Returns:
- self.valor: float of the exchange rate for the specific date
- Arguments:
- CotacaoDolarHistorico: gets a list of USD/BRL exchange rate for a range of dates
- Arguments:
- Start Date: string with date formatted as DD/MM/YYYY
- End Date: string with date formatted as DD/MM/YYYY
- Returns:
- self.cotacoes: list of tuples in the format [Date, Exchange Rate]
- self.itens: total itens in the list
- Arguments:
- FII: colects data for Brazilian real estate funds
- Arguments:
- list that will be populated with funds data
- Returns:
- populated list
- Arguments:
Version history
3.0.1
- Included parameter to limit the number of FIIs fetched. This will be used for testing the full MagicFII program
3.0.0
- Released the FII module to colect data for Brazilian real estate funds
2.3.7
- Changed from a single module ('mftoolbox') containing all classes and functions to a multi-module approach
- Changed internal imports to hide objects that don't need to be exposed (import xxx as _xxx)
- implemented error handling to cotacaodolar module
2.3.0 - 2.3.6
- perfecting the process of package generation. No changes to code
1 maintainer
Metadata
1 maintainer
Release files for mftoolbox 5.0.5
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 | |
|---|---|---|---|---|
| mftoolbox-5.0.5.tar.gz | 19.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mftoolbox-5.0.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 52.3 kB
Release files / mftoolbox-5.0.5.tar.gz
| Download URL | mftoolbox-5.0.5.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dedcc13bae9a2ac74a4bd39e3dce6832ffd7b339062990df578eb000585e0505
|
|
BLAKE2b-256 checksum How to use checksums |
d1fd239cc3dcbbf32d7da6ee2a84beda58dfb959933e603dd1389d0719251909
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.8.8
|
Release files / mftoolbox-5.0.5-py2.py3-none-any.whl
| Download URL | mftoolbox-5.0.5-py2.py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
627aa5b1a40f0d94ce5abd7685834157653ec67678f0d8901c1797f62ef8a4d0
|
|
BLAKE2b-256 checksum How to use checksums |
f63f6e8ef3585b945889240a765c24eab783001cb0c5d8c47db07eb43b6a461b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.8.8
|
Security for mftoolbox 5.0.5
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.
