wakatime-cli VS Nuitka

None of those use the recommended wakatime-cli, which would solve most of these issues. You're getting Linux instead of Windows sometimes because the plugin's User-Agent header isn't consistent when sending heartbeats to the WakaTime API, sometimes using the default Unity header and sometimes using a custom header.

Search for the WakTime extension in your IDEs extension's marketplace or follow the Official Plugins Docs

WakaTime tracks programming activity. The heavy lifting is done by the external WakaTime CLI, so the extension itself must be super lightweight right?

Wakapi is a Wakatime compatible open-source backend for collecting and visualizing coding statistics. It can be self-hosted fairly easily be running the provided Docker image. The compatibility with Wakatime is a big bonus since Wakatime provides many plugins for data collection from your favorite IDE or text editor. I'm pretty sure you can find an integration for your most loved tool here. Let's see how one can run Wakapi with Docker.

What's the recommended way to prevent my open source program from being flagged as false-positive malware on every release? [0] It also seems to be preventing the open source vscode plugin from reading a necessary config file in the user's home directory. If it's not possible to prevent the false-positives is there some way to detect if reading a file fails because of Defender vs. other reasons, like file not exists?

[0] https://github.com/wakatime/wakatime-cli/issues/660

I really tried to use PyInstaller and Nuitka to deploy a Python command line [1] to Windows, Mac, and Linux users. We couldn't get around some system dependencies like OpenSSL needing to be available and not broken on user machines. We ended up re-writing the whole program from Python into Go [2].

Using Go solved so many long-tail bugs for us and just simplified the whole process of shipping code to user machines.

[1] https://github.com/wakatime/legacy-python-cli

[2] https://github.com/wakatime/wakatime-cli

Fixed with https://github.com/wakatime/wakatime-cli/commit/56a85c90fd824c8f930f2b3a9f104872e48d6b01.

Thanks for the feedback! I'm Syrus, main author of the work on py2wasm.

We already opened a PR into Nuitka to bring the relevant changes upstream: https://github.com/Nuitka/Nuitka/pull/2814

We envision py2wasm being a thin layer on top of Nuitka, as also commented in the article.

From what we gathered, we believe that there's usefulness on having py2wasm as a separate package, as py2wasm would also need to ship the precompiled Python distribution (3.11) for WASI (which will not be needed for the other Nuitka use cases), apart of also shipping other tools that are not directly relevant for Nuitka

This is a good place to mention https://nuitka.net/ which aims to compile python programs into standalone binaries.

For Python, you could make a proper deployment binary using Nuitka (in standalone mode – avoid onefile mode for this). I'm not pretending it's as easy as building a Go executable: you may have to do some manual hacking for more unusual unusual packages, and I don't think you can cross compile. I think a key element you're getting at is that Go executables have very few dependencies on OS packages, but with Python (once you've sorted the actual Python dependencies) you only need the packages used for manylinux [2], which is not too onerous.

[1] https://nuitka.net/

[2] https://peps.python.org/pep-0599/#the-manylinux2014-policy

glee is rich in blogging features but has some drawbacks. One of the main drawbacks is its compatibility with multiple operating systems and system architectures. We lost one potential customer due to glee incompatibility in macOS. Another major issue is the deployment time. We built the first version of glee entirely in Python and used nuitka, nuitka compiles Python programs into a single executable binary file. We need to create three separate stages for creating executable binaries for Windows, Mac, and Linux in deployment, and it takes around 20 minutes to complete.

There is already an AOT compiler for Python: Nuitka[0]. But I don't think it's much faster.

And then there is mypyc[1] which uses mypy's static type annotations but is only slightly faster.

And various other compilers like Numba and Cython that work with specialized dialects of Python to achieve better results, but then it's not quite Python anymore.

[0] https://nuitka.net/

[1] https://github.com/python/mypy/tree/master/mypyc

Nuitka deals pretty well with those in general: https://nuitka.net/

Hi HN,

Has anyone explored Nuitka [1] and developed understanding from a blank slate?

Is there any toy version of this, so that one can start playing with the language translation concepts?

Is there any underlying theory/inspiration upon which this project is built?

Are there any similar projects, in say other languages?

[1] https://github.com/Nuitka/Nuitka

That's more of cultural problem in the Python community.

If I provide an end user software to my client written an Python (so not a backend, not a lib...), I will compile it with nuitka (https://github.com/Nuitka/Nuitka) and hide the stack trace (https://www.bitecode.dev/p/why-and-how-to-hide-the-python-st...) to provide a stand alone executable.

This means the users don't have to know it's made with Python or install anything, and it just works.

However, Python is not like Go or Rust, and providing such an installer requires more than work, so a huge part of the user base (which have a lot of non professional coders) don't have the skill, time or resources to do it.

And few people make the promotion of it.

I should write an article on that because really, nobody wants to setup python just to use a tool.

As for a simpler option, you could use a "compiler": https://github.com/Nuitka/Nuitka