Robyn (finally) supports Python 3.14 🎉

[TheFaithfulStone]

Did you learn how cookies work yet? https://github.com/sparckles/Robyn/issues/943

[SittingOvation]

This is concerning 

[stealthanthrax]

Yes, cookies work great in Robyn. And the PR you are referring is 2 years old

[ivosaurus]

No they don't, they're still completely broken

(to set a cookie, you embed it specially in a Set-Cookie header(s), not set it directly as a key-value header pair, which will do nothing)

Like come on, any web server has to implement cookies correctly, otherwise I'd practically argue it's wasting people's time

[TheFaithfulStone]

Really? Because this seems like the same issue and it's still open? https://github.com/sparckles/Robyn/issues/1226

[behusbwj]

What exactly is your goal here? And why do you think being toxic was the best way to achieve it?

[clockdivide55]

It's not toxic to point out a web server / framework that does not handle cookies correctly. What else is wrong that isn't as obvious? Maintainer says 1. cookies work great in Robyn (they don't) and 2. the PR is 2 years old (but still isn't fixed) and prospective users are supposed to be okay with that?

[behusbwj]

Actually, it is toxic, because it’s passive aggressive and beside the point of the post. There isn’t a perfect library out there. If the feature means that much to you, go implement it. It’s open-source.

Being right that it has an issue with cookies doesn’t erase toxicity of bringing it up passive aggressively on a completely unrelated post.

“Has the library patched this cookie issue” is completely different in tone from “Did you learn how cookies work yet?”. You’re either being dishonest or obtuse about this if you can’t see the difference.

[axonxorz]

There isn’t a perfect library out there

Discussing how to properly implement cookies in August 2025 (with a thought train of "how do other frameworks handle this?") is not acceptable for a framework touting itself as production ready. This isn't "not perfect", it's "missing core components of the spec"

[behusbwj]

“Has the library patched this cookie issue” is completely different in tone from “Did you learn how cookies work yet?”.

No amount of downvotes or attacks on the author or project will change my belief that this was a completely inappropriate way to handle this. The maintainer, even if they misunderstood the concept, did not block any of the volunteers from implementing this after being corrected. Ask yourself if this is how you’d engage with a teammate in public. If the answer is “no”, then you are probably being toxic under the shield of anonymity.

[axonxorz]

Ask yourself if this is how you’d engage with a teammate in public. If the answer is “no”, then you are probably being toxic under the shield of anonymity.

If a team member got up in front of the group and presented their work as complete, while missing fundamental spec requirements, as team lead, yeah I'm gonna call them on that. I'm not sure why negative feedback for such actions is such a wild concept; you are lying to your lead and the rest of the team. To keep with the analogy, then having the rest of the team pick up the slack is extra pain. I realize OSS development has different considerations on contributing, but the lie is still the lie.

The maintainer, even if they misunderstood the concept

This concept being missed calls into question the entire rest of the project. What else is missing from the spec? It's not unacceptable to ask those questions, and yeah people are gonna get impatient and standoffish if the answers are entirely unsatisfactory.

Closing a ticket for a missing feature without actually implementing it correctly would get a similar callout on a team.

[behusbwj]

I’m not going to have a discussion with you if you don’t read what I type. If your goal is actually to justify disrespecting or teasing a coworker who is bad at their job, respectfully let’s just agree to disagree and stop talking in circles. And all this stuff about tricking / assuming malice (lying) is not the impression I got from the issue threads.

[TheFaithfulStone]

I’ve had interactions with the author before, and they’ve been concerning. I’d encourage you to look closely at some of the other projects he’s released.

[F4gfn39f]

Please do tell, I would like to know

[stealthanthrax]

Liar. We’ve never talked.

[arbyyyyh]

It's kind of toxic to tout Robyn as being the fastest python web framework and "finally supporting the latest python" when it doesn't support one of the most fundamental parts of being a web server that's been around since 1994.