Electrum rewrite in C

[paeidovyn]

I've experienced a lot of issues with Python modules not being compatible with electrum. This also applies to other Python scripts, though I want to concentrate on Electrum. I've submitted an issue as a feature request on GitHub.

The logical conclusion to the Python ouroboros is to port Electrum to C.


>>This is not an issue with virtual environments, rather an issue with unreliable module compatibility.<<
>>A typical user is never going to resolve this, therefore any application released in Python must be considered non-production.<<

[ABCbits]

I've experienced a lot of issues with Python modules not being compatible with electrum. This also applies to other Python scripts, though I want to concentrate on Electrum. I've submitted an issue as a feature request on GitHub.

The logical conclusion to the Python ouroboros is to port Electrum to C.

Did i miss something? If you or regular user only want to run Electrum, you could download binary from https://electrum.org.

[pooya87]

Correct me if I'm wrong but this sounds like a problem that you have with Python language not with Electrum and I don't see how translating the whole thing to another language like C would solve anything. You should try to improve your Python skills to be able to apply the changes or additions that you want to Electrum.

[NotATether]

You can solve this problem with python virtualenvs. A virtualenv lets you create a brand-new python installation where you can install packages without interference from other packages. Using:

Code:

python -m venv ~/electrum
~/electrum/bin/activate
pip install electrum # replace this with the actual file name, of course
~/electrum/bin/electrum # Where the launcher will be ocated
deactivate

You can make a venv just for Electrum and free up your primary site-packages for everything else. No need to port to C.

[ABCbits]

I see OP edited his thread to add more clarification, so i decide to add new reply.

>>This is not an issue with virtual environments, rather an issue with unreliable module compatibility.<<

In that case, why don't you ask people who create the module/library to pin required library to specific version. For example,

Code:

requests==2.31.0

>>A typical user is never going to resolve this, therefore any application released in Python must be considered non-production.<<

Typical user doesn't have to touch Python anyway. They should just run installer or portable executable which already contain all required file. Electrum already does that with installer, portable version and AppImage.