yes, I'm very sorry but I don't want the user to have a bad experience!! So that's why they need to downgrade to that version, so that everything can work fine. Thank you!!

[–] Eheran@lemmy.world 20 points 11 months ago

I am sorry. What? The bad experience starts with that requirement and for many it might never get anywhere else.

[–] agent_flounder@lemmy.world 15 points 11 months ago

Is it a question of not having tested on the newer version? Asking a user to downgrade their python version is kind of a big ask. I'm only saying this to be of help. Not sure what your experience level is.

I can't imagine there would be massive incompatibility problems between patch releases of Python? Patch releases are supposed to be backwards compatible and I would expect that is especially true for a language like Python or Java or whatnot.

I suppose you could check release notes to see if there are breaking changes. If there is some proven incompatibility perhaps there's a way to work around it somehow. Like, check python version and if version > x run A else run B?

That would be preferable to requiring users to run a specific patch level. Chances are minor versions are probably compatible or mostly so.

It might be more efficient to simply set up an environment to test your code on a newer version if you haven't done so. Like, doing an install of a newer version in a dedicated directory which you use for coding. Or set up a VM. Something like that.

Maybe bundling your preferred python version with the app is an option too.

[–] Sakychu@lemmy.world 5 points 11 months ago

May I then recommend to update your project description to better reflect your intentions. Something like: "Python: 3.10.12 (newer Version may break)" or "For best experience use Python 3.10.12!" Those are by any means just recommendations! P. S: I like your UI design, it is something unique and refreshing!