|
|
Log in / Subscribe / Register

Convenience of developing in Python

Convenience of developing in Python

Posted Jul 22, 2025 7:23 UTC (Tue) by taladar (subscriber, #68407)
In reply to: Convenience of developing in Python by farnz
Parent article: Following up on the Python JIT

But that is exactly my point, at that point you would have to ship the Python version, the one people earlier claimed was "just for prototyping". That is why I wouldn't want to show that one to the customer because at that point I am stuck supporting that language that is completely unmaintainable.


to post comments

Convenience of developing in Python

Posted Jul 22, 2025 9:33 UTC (Tue) by farnz (subscriber, #17727) [Link]

You can ship the Python version as 1.0, and rewrite (using PyO3 or similar if you want to use Rust, or PyBind11 if you want to use C++) for 1.1.

The other thing you can do to reduce your Python maintenance burden (and move it to other languages) is port stable areas of the code into your other language as you go along. Once you're confident that you've extracted all the requirements relating to a given area of the codebase, you can wrap it up for Python to access, and stop maintaining the Python version. You don't have to wait until the project as a whole is done to do this to components.

Convenience of developing in Python

Posted Jul 22, 2025 9:38 UTC (Tue) by anselm (subscriber, #2796) [Link]

that language that is completely unmaintainable

Speak for yourself. Where I work, we make a pretty good living out of maintaining and extending Python code that has been around – at least in part – for a very long time. IMHO, there are popular programming languages which are way less maintainable than Python.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds