atom, pymakr and linter-pylint

  • After a few too many run-time syntax errors, I decided to have a play with the linter-pylint plugin for atom.

    It works, but it does moan mostly about imports that it can't find. Does anyone have any tips to help me resolve the missing imports on my Linux dev box?

  • Hi there,

    I'm Jos , the author of the stubbing tool created to solve my personal frustration

    If there is interest I would be happy to provide support for intellicode and static typechecking for pycom boards.
    My primary focus is VSCode and PyLance, but the stubs are stand based stubs so any IDE and tool can be configured to use them

    For me the blocking challenge is that I do not have access to any pycom hardware.
    If there are a few people that can spend some time to run a few commands and the firmware stubber on their boards , and share the outcomes of that.

    I think this is quite simple to improve the developing experience and thus the code quality of your projects,

    (having a pycom board to test on won't harm either )

    See Generic procedure for manual stubbing

    Scripts to run :

    Please share results and feedback on

  • I have found this project on github that aims to resolve this kind of issue.
    I wonder if Pycom might contribute to it, to enable pukka linting of code in Atom/Pymakr.

  • Having shared my code with a friend who has recently bought a bunch of LoPy4's, he is now experiencing the joys of runtime syntax errors as he learns about micropython development.
    I wonder if anyone has further explored the idea of using a linter in Atom and found one that is less spammy than linter-pylint in terms of false positives for micropython imports?

Log in to reply

Pycom on Twitter