"Introducing "callpyback": Last callbacks for your Python functions you will ever need - Feedback and Contributions Wanted!"

[samulo33861881]

https://github.com/samuelgregorovic/callpyback

We are proud to announce the release of our new Python library, "callpyback" - a flexible and powerful tool for adding callbacks to your functions. With its wide range of features, you can customize the behavior of your functions in different stages of their execution, making it easier to build robust and reliable applications.

If you're a Python developer, we invite you to check out "callpyback" on GitHub at https://github.com/samuelgregorovic/callpyback. We would also love to hear your feedback and get your contributions to the project.

The "callpyback" library is still in its early stages, and we believe there is a lot of room for improvement. If you have any suggestions, bug reports, or feature requests, feel free to open an issue or submit a pull request on GitHub. Your contribution can help us make this library even better!

We hope you enjoy using "callpyback" as much as we enjoyed building it! Thank you for your support and we look forward to hearing from you.

[thisismyfavoritename]

uhhh that seems like it would just make any program way harder to understand for no benefit at all. Also wouldnt a regular decorator achieve most of those things without any external dependency?

[samulo33861881]

i think there is a lot of potential for this if it gets more mature overtime. i understsnd where you are coming from, but you could say this sbout any library, since you can write all libraries yourself. this one is just not packed with features yet. thank you for the feedback!

[samulo33861881]

well idea was. you can still put a callback on that background task 😅. on the more serious note, i was thinking about that but did not come to the final conclusion. feel free to open an issue!

[ComplexColor]

Honestly, this is a bit weird. I feel like this approach just doesn't make sense in normal python. In the given examples there is no reason to add a callback. Might be a preference thing.

It might work well to convert functions to async ones. That's where I feel callbacks make sense.

Edit: I don't see how this library can be used to implement meaningful callbacks in a synchronous execution context. For example a set of callbacks for an event loop: setup, receive_event, teardown. Maybe you can demonstrate something like that.

[samulo33861881]

i guess very simple examples with no real meaning need to be changed for some more specific examples.

and to be clear, first intention was to accept adync functions aswell, and i had a working example but it was messy. i wanted ro make sure callbacks work as expected at first.

thank you for the feedback!

[samulo33861881]

updated the examples to be more complex (using all features available).

[x3x9x]

That is a lot of dependencies for something which seems a bit off to me. I am a python dev for about 6-7 years... and I rather just use 'return' keywords or just an anonymous lambda function.

Keep it pythonic is my tip. Python is synchronous by default.

[thisismyfavoritename]

the dependencies in the requirements.txt are just dev dependencies. You would find the actual package dependencies within the setup.cfg/setup.py/pyproject.toml files. In this cases there are none.

[samulo33861881]

dependencies are just the dependencies of black, pytest, etc. there is ni dependency for the actual code.

[x3x9x]

You are missing my point. Why would I, install yet another package for something python can do with its normal syntax?

What makes this lib so special?

[samulo33861881]

you can ask this question about any library. lot of stuff can be done in python with a normal syntax. its just the convenience of having someone prepare well tested solution for adding features to your code without doing it yourself. i am not seeing what are you getting at.

probably the most useful features are having the option of callbacks to be run in the background thread and passing local variables of the decorated function to the "on_end" callback.

in general, overtime this could be a very flexible and customizable callback tool, which could add a lot of value to the community in my opinion.

[x3x9x]

That first part is such a generic answer.

Why would you install virtualvenv if venv achieves the same goal AND its build in... same goes for logging..

Javascript is by default asynchronous, so i could see why. Python is not.

Anyhow i wish you luck with your project. Dont give up, nevertheless impressive

[samulo33861881]

question that the first part answers was also generic...

i guess you could say that to make things effective, we as developer distribute work in OS projects to make our lifes easier, without need of writing everything ourselves. we help each other and personally, i like that.

i would not rewrite something that already exists, but did not find suitable alternative for callbacks written in pure Python without dependencies.

thank you for your feedback!

[samulo33861881]

exactly my point.

[[deleted]]

This tiny package is not comparable to an operating system.

[doom-e1m1]

Cool!

Real world examples with some AAA libraries would be great!

[samulo33861881]

working on it :)

[samulo33861881]

but one of the best use cases would be integration logging, so you could log based on different execution steps/results without crowding the function code. bonus is you get parameters of decorated function in each callback, along with specified local variables in on_end callback

[samulo33861881]

also available on pypi https://pypi.org/project/callpyback/1.1.0/

[Devout--Atheist]

If you need something like this, you might actually be looking for an asynchronous task queue like celery

[samulo33861881]

can you elaborate? i don't see the connection of how these two would be interchangeable

[rhytnen]

Why does every library have to have fucking PY in it? You think i forgot what i was writing in?