Why Fryers?
The reason i created this wrapper module for the
fyers_apiv3module provided by the Fyers platform is because one has to make sure the access token is valid and if not generate new access token or use refresh_token, which added overhead to the scripts created using this module. But my wrapper takes care of all that.
We Just have to provide my wrapper class
Fyerswith theclient_id,secret_keyand thepin. Once thats given, the login flow will be taken care of and we can enjoy the scripting without any hassel.
How to Install
pip install fryers
Simple way to use
We can use this module for login flow and then use the native fyersModel instance to interact with the API.
Simple code to do this would be
from fryers import Fyers
client_id = "xxxxx"
secret_key = "xxyyxyxy"
pin = "4783"
# Fyers logins automatically uses a saved token, if exists
# otherwise it re-initiates the login flow
# it outputs the returned URL which user has to visit
# and then copy the auth_code from there and paste it in the terminal
fyers = Fyers(client_id, secret_key, pin=pin) # creates a file tokens.txt where tokens are stored
# grab the native instance and use native api
native_fyers = fyers.get_native_instance()
# we can use native api from (native_fyers) which is an instance of FyersModel
NOTE
This is current in development, i will be adding more features to make the api easy to use. I will also create a comprehensive documentation for this wrapper so that users dont have an issue using it.
Metadata
Release files for fryers 1.0.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 |
|---|---|---|---|---|
| fryers-1.0.0.tar.gz | 5.2 kB | Without provenance | Details for fryers-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fryers-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for fryers-1.0.0-py3-none-any.whl |
Total release size: 10.5 kB
Release files / fryers-1.0.0.tar.gz
| Download URL | fryers-1.0.0.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d8849ae38673a8733bf4b4e48c5c65ff616104bfec153dfe64bcf61dc145589
|
|
BLAKE2b-256 checksum How to use checksums |
46781a167b9f22d3ada459b0762033207390bd673ab26820353e5558eaf6c046
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / fryers-1.0.0-py3-none-any.whl
| Download URL | fryers-1.0.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17531dcd99be673a5a04ebcf4cecfee4ca9a72e0bc13310bc353bf4a07008f44
|
|
BLAKE2b-256 checksum How to use checksums |
19b82091da14847f3fc8c63085bf7983c06659117263a69720987036a3451f33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for fryers 1.0.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.