1. Nuitka Github
  2. Nuitka Tutorial
Nuitka xp

Nuitka, a compiler that transforms Python into C for the sake of both performance gains and a more portable runtime, has reached its 0.6 release —a milestone that lays the groundwork for future. Apr 28, 2021 Nuitka. Rather than replace the Python runtime, some teams are doing away with a Python runtime entirely and seeking ways to transpile Python code to languages that run natively at high speed. Case in point: Nuitka, which converts Python to C code—and can automatically pack up all of the files needed from the CPython runtime to boot. Apr 18, 2021 Nuitka is the Python compiler. It is written in Python. It is a seamless replacement or extension to the Python interpreter and compiles every construct that CPython 2.6, 2.7, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9 have, when itself run with that Python version. With nuitka-setuptools this wheel can be devoid of pure python and only contain compiled code which is not only faster (quote: Nuitka is more than 2 times faster than CPython) but has a relatively high level of code security. Basic Usage: $ nuitka -recurse-all -recurse-stdlib Compile a Python program '' and the modules it uses to an executable 'someprogram.exe'. Keep the debug information, so valgrind, gdb, etc.

Nuitka vs pyinstallerNiurka

Nuitka Github


Nuitka Tutorial

On Wed, Jul 4, 2012 at 3:19 PM, Paul Boddie <[email protected]> wrote:
> On Wednesday, 4 July 2012 14:56:21 UTC+2, Guido van Rossum wrote:
>> On Wed, Jul 4, 2012 at 2:48 PM, Sebastien Douche <[email protected]>
>> wrote:
>> > On Wed, Jul 4, 2012 at 11:08 AM, Guido van Rossum <[email protected]>
>> > wrote:
>> >
>> >> In the end it was an utter disappointment. The project's (and the
>> >> talk's) focus are all wrong.
> Ouch, poor guy!
>> > Can you explain more in depth why the project is wrong?
>> The guy only reported on the boring parts, which he completed
>> successfully -- e.g. project management, faithfully translating
>> everything to C++ (deferring to CPython for all the object
>> implementations). He seems to believe that doing optimizations is now
>> going to be easy, but his ideas are very shallow -- constant folding,
>> for example.
> I guess the hope is to use this work as the basis for further work that
> incorporates more sophisticated analysis techniques. In itself, I don't see
> that as a bad thing, and we have to give people the opportunity to change
> their mind and their project's direction, too, as they refine their
> strategy.
What he's building is not likely to be a good platform for
experimentation with optimization techniques. Even more so because he
is incredibly naive about what kind of optimizations he'd like to
apply. (He basically doesn't seem aware of the difficulties arising
with static analysis of Python.)
> While we're on the subject of existing projects, do you have an opinion
> about PySonar? It's a project done by an intern at Google that follows on
> from some code Google contributed to Jython for Python source indexing.
> Since nothing Python-related at Google can possibly escape your notice, and
> given that it supposedly supports a service internally, I wondered if you
> have any thoughts about it or whether it has shaped your recent thinking.
> This would have been a great 'ask the BDFL' question at EuroPython, of
> course. ;-)
> Paul
> PySonar:
Yeah, I chatted with Yi for a bit before he left Google. I don't think
his code is still in use. IIRC he's really not interested in analyzing
full Python; he's more interested in a less dynamic subset that is
easy to analyze.
More promising seems to be HotPy (2), which Mark Shannon is talking
about at EuroPython right now.