Skip to content

Comments

Update README with new function documentation#1

Open
DarkLord017 wants to merge 6 commits into0-th:dev(wip)from
DarkLord017:dev(wip)
Open

Update README with new function documentation#1
DarkLord017 wants to merge 6 commits into0-th:dev(wip)from
DarkLord017:dev(wip)

Conversation

@DarkLord017
Copy link

Adding documentation

Added documentation for abort, all_, and batch functions.
@DarkLord017
Copy link
Author

@0-th started working on documentation pls review n lmk

@DarkLord017 DarkLord017 marked this pull request as ready for review January 30, 2026 19:29
Copy link
Owner

@0-th 0-th left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great effort here @DarkLord017 . I appreciate it.

I'd merge this right away once you've made necessary changes.

Also, I'd prefer if you didn't just pull in-code comments into the readme for documentation of the library APIs, and instead just documented similar to the reference implementation. see here.

I think the documentation would overall be much improved if the library was documented (not strictly or per-word) similarly to the reference implementation. At least it would be a really good start, coupled with the changes I requested in my review.

Thanks for the effort again.

README.md Outdated
# Class refrences

An implementation of [actor](https://github.com/Gozala/actor) in Python.
## Future
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the Future_ class was only meant to be inherited by the Fork class to make it await-able, it doesn't serve any other purposes outside of this.

doesn't need to be documented on here.

## Future
Provides Promise-like interface for tasks, enabling them to be awaited from async contexts.

## Install
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think install instructions should be retained in the docs, but since it's yet to be published on PyPI, it could be edited later as the package name on PyPI might be subject to change

README.md Outdated

An implementation of [actor](https://github.com/Gozala/actor) in Python.
## Future
Provides Promise-like interface for tasks, enabling them to be awaited from async contexts.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Provides Promise-like interface for tasks, enabling them to be awaited from async contexts.

# actress
# Class refrences

An implementation of [actor](https://github.com/Gozala/actor) in Python.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this description should be kept as well. seems accurate to me.

README.md Outdated
Comment on lines 103 to 109
**Abort handling:**
```python
# Abort all idle tasks and re-enqueue them
for task in group.stack.idle:
yield from abort(task, error)
enqueue(task)
```
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Abort handling:**
```python
# Abort all idle tasks and re-enqueue them
for task in group.stack.idle:
yield from abort(task, error)
enqueue(task)
```

README.md Outdated
Comment on lines 110 to 113

Idle tasks may still have cleanup code (finally blocks), so:
- They are aborted
- Then re-enqueued so the abort fully completes
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Idle tasks may still have cleanup code (finally blocks), so:
- They are aborted
- Then re-enqueued so the abort fully completes

# {"type": "read", "read": "read2"}
```

## Usage
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should keep the Usage section as well as it adds expected structure you'd find in documentations of Python libraries, similar reason to why I think you should keep the Installation section as well

main(run_all())
```

## Contributing
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should add a general contribution guideline too.
e.g to install dev dependencies run: pip install -e ".[dev]", run tests: pytest, etc... things like that

Comment on lines 19 to 23
All welcome! storacha.network is open-source.

## License

Dual-licensed under [Apache-2.0 OR MIT](LICENSE.md)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should retain the original licensing as well as we'll ultimately still be getting this branch merged into the main repo in the storacha org.

@DarkLord017 DarkLord017 requested a review from 0-th February 18, 2026 00:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants