Closed Kusoneko closed 4 years ago
Weird. I'll take a look.
It looks like the reason is a two-day old change in ZeroNet core. I was going to make a PR to support different cryptographies (e.g. Ethereum, Ark and such, non-ecc) so I added src/Crypt/Crypt.py
to my local fork and used try/except to use it if available. It usually wasn't on most machines. Unfortunately, nofish added this file but with different contents, so Python imported wrong code and thus PeerMessage couldn't find some functions. I'll fix this later today.
@imachug Ping...
Kinda forgot about that... should be fixed now, thanks.
I'm running Arch Linux (which now uses python 3.8 if that's in any way relevant) When starting Zeronet (latest revision), both PeerMessage and BackgroundProcessing give out an error due to a line in BackgroundProcessing's crypt.py: