Skip to content

Fix: Harden Python client runtime correctness, bounded I/O, and secret hygiene #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mertcano wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix: Harden Python client runtime correctness, bounded I/O, and secret hygiene #136

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bfbf7d1
Fix: Harden Python client runtime correctness, bounded I/O, and secre…
mertcano Aug 20, 2026
067e210
Update .gitignore to include additional patterns
mertcano Aug 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,8 @@
__pycache__/
*.py[cod]
.env
__pycache__
.env.*
!.env.example
# SECURITY FIX: Ensure private key artifacts are ignored from version control.
*.pem
*.key
14 changes: 12 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,20 @@
Markdown
# kalshi-starter-code-python
Example python code for accessing api-authenticated endpoints on [Kalshi](https://kalshi.com). This is not an SDK.

## Installation
Install requirements.txt in a virtual environment of your choice and execute main.py from within the repo.

```
pip install -r requirements.txt
python main.py
```


## Configuration

Create a `.env` file or export the following variables before running the example:

```text
KALSHI_ENV=demo
DEMO_KEYID=your-demo-key-id
DEMO_KEYFILE=~/path/to/demo-private-key.pem
Use the corresponding PROD_KEYID, PROD_KEYFILE, and optional PROD_KEY_PASSWORD variables when KALSHI_ENV=prod. The private-key file must remain outside version control; encrypted PEM files can be used with the matching *_KEY_PASSWORD variable.
Loading