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

    urequests and r.close()

    Scheduled Pinned Locked Moved Getting Started
    urequestsr.close
    1 Posts 1 Posters 225 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.
    • K Offline
      kjm
      last edited by

      The text book says

      n=1; m=n 
      

      doesn't create a new object for m it just references the same object that n is referencing.

      When I do

      r=urequests.get('https://someurl'); val=r.text; r.close(); return val
      

      why does val still retain it's value when r.close() destroys the urequests return object? I came up with the above because

      r=urequests.get('https://someurl'); r.close(); return r.text 
      

      caused OSErrors from urequests. But now I'm wondering why it works?

      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