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

    NameError: name '​' is not defined when upload the "Lopy to Lopy" example

    Scheduled Pinned Locked Moved MicroPython
    fipyloramain.pymicropythonatom
    3 Posts 2 Posters 1.1k 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
      grideagle
      last edited by

      I can run the "Lopy to Lopy" example code from Atom on my FiPy, but when I do the upload from Atom I get the "NameError: name '​' is not defined" error on line 4. Line 4 is a blank line in the example. Looking for some help please.

      Uploading project (main folder)...
      Not safe booting, disabled in settings
      Reading file status
      [1/3] Writing file boot.py
      [2/3] Writing file main.py
      [3/3] Writing file mymain.py
      Upload done, resetting board...
      OKets Jun 8 2016 00:22:57

      rst:0x7 (TG0WDT_SYS_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
      configsip: 0, SPIWP:0xee
      clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
      mode:DIO, clock div:1
      load:0x3fff8028,len:8
      load:0x3fff8030,len:1728
      load:0x4009fa00,len:0
      load:0x4009fa00,len:14584
      entry 0x400a059c
      Traceback (most recent call last):
      File "main.py", line 4, in <module>
      NameError: name '​' is not defined
      Pycom MicroPython 1.18.1.r1 [v1.8.6-849-b0520f1] on 2018-08-29; FiPy with ESP32

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

        I think I found the problem. For some reason there were extra unprinted characters added to the blank lines when doing the copy-paste from the example documentation.

        danD 1 Reply Last reply Reply Quote 1
        • danD Offline
          dan @grideagle
          last edited by

          Hi @grideagle,

          Thank you for reporting that, I've reported it to GitBook. The current workaround is to use the "copy" button it the top right corner of the code section.

          1 Reply Last reply Reply Quote 0

          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