helius-python 0.4.0__tar.gz → 0.4.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {helius_python-0.4.0 → helius_python-0.4.1}/PKG-INFO +14 -1
- {helius_python-0.4.0 → helius_python-0.4.1}/README.md +13 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/pyproject.toml +1 -1
- {helius_python-0.4.0 → helius_python-0.4.1}/.editorconfig +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/.github/ISSUE_TEMPLATE/bug_report.yml +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/.github/ISSUE_TEMPLATE/config.yml +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/.github/ISSUE_TEMPLATE/feature_request.yml +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/.github/workflows/python-package.yml +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/.github/workflows/python-publish.yml +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/.gitignore +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/AGENTS.md +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/CLAUDE.md +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/CONTRIBUTING.md +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/LICENSE +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/TODO.md +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/laserstream/websocket_logs.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/address_transactions.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/address_transfers.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/block_explorer.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/devnet_airdrop.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/network_status.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/priority_fees.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/stake_overview.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/token_inspector.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/transaction_inspector.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/solana_rpc/wallet_tracker.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/webhooks/webhook_crud.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/examples/webhooks/webhook_receiver.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/requirements.txt +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/__init__.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/admin/__init__.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/admin/admin.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/laserstream/websockets.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/solana_rpc/__init__.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/solana_rpc/client.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/solana_rpc/models.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/utils/__init__.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/utils/json_rpc_request.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/webhooks/__init__.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/src/helius/webhooks/webhooks.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/test_examples.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/fixtures/account.json +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/fixtures/supply.json +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/admin/test_admin.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/lasterstream/test_websockets.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/solana_rpc/test_client.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/solana_rpc/test_models.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/utils/test_json_rpc_request.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/webhooks/test_webhook.py +0 -0
- {helius_python-0.4.0 → helius_python-0.4.1}/tests/unit/webhooks/test_webhooks_api_client.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: helius-python
|
|
3
|
-
Version: 0.4.
|
|
3
|
+
Version: 0.4.1
|
|
4
4
|
Summary: Typed Python client for the Helius API
|
|
5
5
|
Project-URL: Homepage, https://github.com/markosnarinian/helius-python
|
|
6
6
|
Project-URL: Issues, https://github.com/markosnarinian/helius-python/issues
|
|
@@ -431,6 +431,19 @@ client defaults to `https://admin-api.helius.xyz` and, like the others,
|
|
|
431
431
|
supports the context-manager protocol, a manual `close()`, and reads
|
|
432
432
|
`HELIUS_API_KEY` from the environment or `.env`.
|
|
433
433
|
|
|
434
|
+
## AI
|
|
435
|
+
AI was used to assist in the development of this project, which was started beacause I needed a Helius client written in Python myself for another project. It has eliminated the need to perform repetitive tasks, such as writing functions that are similar to those written by hand before them. It has also been useful in drafting and updating the documentation (exclusively README.md at the time of writing), writing tests and examples.
|
|
436
|
+
That said, AI-generated code is reviewed in full, line-by-line by human(s) against the Helius API specifications.
|
|
437
|
+
|
|
438
|
+
To roughly describe my approach to using AI in this project, I generally write the code by hand, which makes it easy to structure the code well and maintain an intuitive understanding of how the code works. Then, when I got to the part where I had to implement 100+ similar Python functions, I turned to AI to write the massive part of the codebase, while I reviewed the result at the same time.
|
|
439
|
+
|
|
440
|
+
To sum up:
|
|
441
|
+
- I generally structure** and write a good part of what I'm programming by hand, including boilerplate.
|
|
442
|
+
- I find it best to prompt agents to implement very limited functionality within narrow scope, performing something closer to pair-programming.
|
|
443
|
+
- Even though at least half the LoC in this project are hand-typed, I find that AI is incredibly capable, can be enjoyable to use, but most importantly, using AI allows me to focus my time and energy on what matters.
|
|
444
|
+
|
|
445
|
+
By the way, this README section is completely brain-made and hand-typed.
|
|
446
|
+
|
|
434
447
|
## License
|
|
435
448
|
|
|
436
449
|
[MIT](LICENSE)
|
|
@@ -409,6 +409,19 @@ client defaults to `https://admin-api.helius.xyz` and, like the others,
|
|
|
409
409
|
supports the context-manager protocol, a manual `close()`, and reads
|
|
410
410
|
`HELIUS_API_KEY` from the environment or `.env`.
|
|
411
411
|
|
|
412
|
+
## AI
|
|
413
|
+
AI was used to assist in the development of this project, which was started beacause I needed a Helius client written in Python myself for another project. It has eliminated the need to perform repetitive tasks, such as writing functions that are similar to those written by hand before them. It has also been useful in drafting and updating the documentation (exclusively README.md at the time of writing), writing tests and examples.
|
|
414
|
+
That said, AI-generated code is reviewed in full, line-by-line by human(s) against the Helius API specifications.
|
|
415
|
+
|
|
416
|
+
To roughly describe my approach to using AI in this project, I generally write the code by hand, which makes it easy to structure the code well and maintain an intuitive understanding of how the code works. Then, when I got to the part where I had to implement 100+ similar Python functions, I turned to AI to write the massive part of the codebase, while I reviewed the result at the same time.
|
|
417
|
+
|
|
418
|
+
To sum up:
|
|
419
|
+
- I generally structure** and write a good part of what I'm programming by hand, including boilerplate.
|
|
420
|
+
- I find it best to prompt agents to implement very limited functionality within narrow scope, performing something closer to pair-programming.
|
|
421
|
+
- Even though at least half the LoC in this project are hand-typed, I find that AI is incredibly capable, can be enjoyable to use, but most importantly, using AI allows me to focus my time and energy on what matters.
|
|
422
|
+
|
|
423
|
+
By the way, this README section is completely brain-made and hand-typed.
|
|
424
|
+
|
|
412
425
|
## License
|
|
413
426
|
|
|
414
427
|
[MIT](LICENSE)
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|