On Sun, Feb 19, 2017 at 12:44 PM, Jan Engelhardt <jengelh@inai.de> wrote:
On Sunday 2017-02-19 16:19, Todd Rme wrote:
On Fri, Feb 17, 2017 at 5:30 PM, Jan Engelhardt <jengelh@inai.de> wrote:
On Friday 2017-02-17 21:55, Todd Rme wrote:
As others have said, Python is an interpreted language, not a compiled language like C.
That's nonsense. Who says Python *has* to be interpreted? Who says C *has* to be compiled? Python, like C, each is a language (with a more or less large standard library behind it).. I have yet to see a language that cannot be compiled - it most likely would be some esoteric one.
I guess in principle it *might* be possible to make a python ahead-of-time compiler, or even a generally-usable python JIT (existing JITs only work in special cases)
do so have failed. Python is just too dynamic a language for this to be feasible.
The very existence of Python JITs goes counter to your claims.
As I said, "existing JITs only work in special cases". There is no existing JIT that can compile the full range of python's capabilities.
It may not necessarily be fast, but it's possible:
I didn't say it wasn't "possible", I said it wasn't "feasible."
"""Every language can be mapped to another language. If not, then the language cannot really run on computers. Thus every language can technically be compiled. And, since any compiled program can be written in the form "interpret the act of compiling the program, then interpret the result," every program can be interpreted as well.""" - http://softwareengineering.stackexchange.com/a/262286
If you read further down, the post is saying the exact same thing I am saying. This discussion is all academic, though. The normal and expected way to distribute Python code includes the source, the Python standard library supports directly accessing the source code, and Python packages are making use of that capability. The only reliable way to make sure that isn't happening is to manually check every .py file in the package (since they may not be directly calling the python standard library functions, or may be accessing the source directly). I hope that for special-purpose source-only distributions they are willing to take the time to verify that the packages they are using don't rely on the source code at least for code paths they are making use of. But we don't even have the manpower to keep all of our existing packages up-to-date. It is simply infeasible for us to check that each update of each package isn't introducing the use of this feature. And anything less than that risks shipping horribly broken code. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org