Error during download and install of Python Mode for Processing 3 about processing4

[pacien]

I'm facing the same issue with Processing 3.5.3 on NixOS (unstable channel).
The same error appears when attempting to download any other library, tool, example or mode.

It is nevertheless possible to download and install those manually by finding the URL of the appropriate ZIP file in the contribs db, extracting it and putting the content in the appropriate folder in ~/sketchbook.

[pacien]

Thank you @pacien . I guess you are on NixOS 19.09 channel... I am still on 19.03 and seems that the Processing package is still the broken one. If so, I should migrate to 19.09, right?

Indeed, it works fine on 19.09 and the unstable channel, besides the downloading problem in the contribution manager as described in this issue.

[villares]

To manually download and install Python Mode:
Download from: http://py.processing.org/3/PythonMode.zip
Unzip, and copy PythonMode into: User/Documents/Processing/modes/
(on *nix it's user/sketchbook/modes/)

[maxdevjs]

@pacien , how did you get Processing to work on NixOS?

[pacien]

@pacien , how did you get Processing to work on NixOS?

I just used the package: https://nixos.org/nixos/packages.html?attr=processing

[maxdevjs]

Thank you @pacien . I guess you are on NixOS 19.09 channel... I am still on 19.03 and seems that the Processing package is still the broken one. If so, I should migrate to 19.09, right?

[maxdevjs]

Thank you again, @pacien , now it works. And, in fact, I was able to install from Processing itself only the Extended Code Completion tool.

[benfry]

Please give this a try with Processing 3.5.4 once it's available. With any luck there should be more detail about what failed (a stack trace) in the console when this happens.

[benfry]

3.5.4 is now available here: https://github.com/processing/processing/releases/tag/processing-0270-3.5.4

Please try it out and let me know what happens so we can get this resolved.

[github-actions]

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.