Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    atom, pymakr and linter-pylint

    Scheduled Pinned Locked Moved Software Tools
    4 Posts 2 Posters 957 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      g0hww
      last edited by

      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?

      1 Reply Last reply Reply Quote 0
      • G Offline
        g0hww
        last edited by

        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?

        1 Reply Last reply Reply Quote 0
        • G Offline
          g0hww
          last edited by

          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.

          https://github.com/Josverl/micropython-stubs

          1 Reply Last reply Reply Quote 3
          • J Offline
            Jos Verlinde
            last edited by

            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 :
            https://github.com/Josverl/micropython-stubber/tree/main/board

            Please share results and feedback on
            https://github.com/Josverl/micropython-stubs/discussions

            1 Reply Last reply Reply Quote 1

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post

            Pycom on Twitter

            Pycom