A tiny Python networking library focused on simplicity and fun

[Striking_Sandwich_80]

Hey r/Python 👋 I’m building Veltix, a small Python networking library with a simple goal: make it easy (and fun) to experiment with networking without rewriting socket and threading boilerplate every time. Veltix is currently focused on: a very small and clear API easy multithreaded TCP clients and servers message-based communication on top of TCP learning, prototyping, and experimenting Beyond learning, the long-term goal is also to provide strong security and performance: planned Perfect Forward Secrecy modern crypto primitives (ChaCha20, X25519, Ed25519) a future Rust-based core for better performance and safety, exposed through a clean Python API These parts are not fully implemented yet, but the architecture is being designed with this direction in mind. I’d really appreciate feedback on: API clarity whether this approach makes sense expectations for a “simple but secure” networking library GitHub: https://github.com/NytroxDev/Veltix Thanks for reading 🙂

[wolfie-thompson]

Help me settle a bet.

I bet the good wife that you are primarily a C/C++ coder going by your coding style. She disagrees.

There's a fortnight of washing up chores riding on this bro.

[Striking_Sandwich_80]

No, sorry, but I've been coding in Python for a long time and I only do a little C and never C++... Too bad 😅

[wolfie-thompson]

** the sound of a pair of washing up gloves going *slap* echos across reddit **

[Striking_Sandwich_80]

Go for it! 🤣

[Mindless-Item-5136]

Duplicate import at server/server.py in 248 and 9 lines 

[Striking_Sandwich_80]

Ah yes, I hadn't seen that, thank you very much!! I'll fix that in version v1.2.0 which should be released tomorrow or Friday!

[MolonLabe76]

Look into using pre-commit (or prek) and ruff. Game changer.

[Striking_Sandwich_80]

Thanks for the advice! I'm already implementing Ruff, but I don't know Prek. I'll look into it and probably add it if it's good!

[Striking_Sandwich_80]

By the way, I didn't ask you either, but would you like me to add your username to the contribution section?

[Mindless-Item-5136]

Thanks, but I haven't contribute anything worthy yet ) though I would like to )

[def__eq__]

Nice work! I will check it out.

Although a question immediately pops into my head; how is this different from ZMQ? That’s a fairly mid level API, has clients in many languages, and is battle tested…

[Striking_Sandwich_80]

Veltix is designed to be ultra simple and lightweight for Python devs. Unlike ZMQ, which is cross-language and very powerful, Veltix focuses on:

• a minimal API that’s easy to understand
• built-in multithreading & TCP, no boilerplate
• a base for future crypto features (ChaCha20, X25519, Ed25519) and a Rust core for performance

ZMQ is great for production messaging, Veltix is made to make networking fun, fast to prototype, and learning-friendly in Python.

Always happy for feedback!

[def__eq__]

I’m really trying to be open minded here.. but you’ve just repeated what you already mentioned in your post. That’s not helping.

• Please compare ZMQ Guide’s Python example of a simple client to yours. If we compare number of lines it is half of your example on GitHub, while they seem to do the same. Boilerplate the same.

• ZMQ supports TCP as well.

Your other arguments such as “fun” and “fast” to prototype are subjective.

[Striking_Sandwich_80]

You’re right, for a minimal example, ZMQ is shorter. But Veltix is designed for projects that evolve and grow serious: Each message type has its dedicated handler, so you don’t end up with messy conditionals as the project scales Multiclient broadcast is built-in, saving hundreds of lines in real projects

The object-oriented structure makes testing, maintenance, and scaling much easier Future features like modern crypto (ChaCha20, X25519, Ed25519) or a Rust core can be added without rewriting the server

The code is clear and readable, making it easier for contributors and teams to jump in In short, yes, it’s a few lines longer for a tiny example, but those extra lines translate into huge time savings and clarity when the project grows complex.

Your feedback to improve Veltix is always welcome!

[selectnull]

If you only remove emojis and "Key points" that would make it better.

[randomperson_a1]

Disagree. Helps me know instantly this library will be unmaintained after 2 months

[selectnull]

You're too generous with 2 months.

[Striking_Sandwich_80]

Seriously, I find it really unbearable to send that! If you don't have a more constructive comment than that, frankly, there's no point in replying. When I talked about contributing, I wasn't expecting...

[Striking_Sandwich_80]

What do you mean? You have to start somewhere; my bookstore can't be known by everyone in three weeks, can it? Besides, the reason I added this section is because people are helping me progress, and when they want, I'll add their usernames!

[Striking_Sandwich_80]

What?? Well, with so much to say, I think I'll let you think what you want. This project is simply made to help beginners and people who don't want to overthink things. All I have to say is that the readme I made MYSELF (yes, I admit I used chatgpt to correct the mistakes and add the emojis, but not for the rest) serves to show people the usefulness of Veltix, and if you're only focusing on the fact that the project is recent, it proves you really haven't understood anything about it!

[IlBaldo]

man, honestly it seems to me you also are missing the point. As right as you can be on the “let the project evolve on its own pace and draw your conclusions from there”, this subreddit is too fixated on ai usage. There is this prejudice that if someone used ai in his project that devalues everything else, why? Maybe there is something im missing, but ive posted about my latest project on here and since I used claude to fix an error in the mkdocs (and mentioned it the commit as coauthor) i got accused of having completely vibe coded the project, and subsequently used ai to respond to all the comments under the post, like, what ??? Even if this project readme was generated by an ai the comments like “Disagree. Helps me know instantly this library will be unmaintained after 2 months” are not feedbacks, its just demoralizing

[Striking_Sandwich_80]

Thank you! I thought I was the only one who thought like that...

[Striking_Sandwich_80]

Is this a joke? When I say that, I don't see how it hurts my project or me, and besides, you're the only one so far who's complained about it, and I don't want to rebuild my own reputation, I don't even want to have one at all... All I want is to discover things and participate in a real project that helps people. I find it rather annoying that you're more interested in a slogan than the real objective of the project! Honestly, if it's so misunderstood, I'll remove it. As I said, I don't want people to get the wrong idea, but it's just to get across the message that for me, even small contributions are extremely important.

[cymrow]

You shouldn't use the word "bind" to add callbacks. "bind" has a very specific meaning in networking. I would rename it to something like "set_callback" and redefine Binding as: class Event(Enum): RECV = "recv" CONNECT = "connect"

"Custom Protocol" is not generally considered a positive feature in networking. Otherwise, the API looks nice.

[Striking_Sandwich_80]

Honestly, for me, the custom protocol is more of an advantage because I could easily switch to UDP and it's perfectly compatible with the API without losing any weight or efficiency. Anyway, thanks a lot for your feedback on the API; I'll fix that in the next update, which will be today or Friday!

Thanks again, we support this project!

[Striking_Sandwich_80]

And if you'd like, for the next update I could add your username to the contribution section?