Client code: ModuleNotFoundError: No module named 'urllib.parse'

nmvega · September 8, 2022, 1:58am

@nickantonaccio @jshaffstall Thanks guys for the CORS heads-up and reminder! I wasn’t even thinking of it.

jshaffstall · September 8, 2022, 2:09am

The tinyurl one might respond correctly if the proper headers are set in the HTTP request. I don’t have experience with that, though, but I suspect you’re right that looking at the Javascript library might shed some light on what headers to send.

nickantonaccio · September 8, 2022, 2:10am

Aha, at first look, it appears the JS code sends a request to https://cors-anywhere.herokuapp.com, which acts as a proxy to handle the CORS issues:

nickantonaccio · September 8, 2022, 2:11am

And it looks like they’re having some problems with abuse:

github.com/Rob--W/cors-anywhere

PSA: Public demo server (cors-anywhere.herokuapp.com) will be very limited by January 2021, 31st

opened 12:26PM - 12 Dec 20 UTC

Rob--W

The demo server of CORS Anywhere (cors-anywhere.herokuapp.com) is meant to be a …demo of this project. But abuse has become so common that the platform where the demo is hosted (Heroku) has asked me to shut down the server, despite efforts to counter the abuse (rate limits in #45 and #164, and blocking other forms of requests). Downtime becomes increasingly frequent (e.g. recently #300, #299, #295, #294, #287) due to abuse and its popularity. To counter this, I will make the following changes: 1. The rate limit will decrease from 200 (#164) per hour to 50 per hour. 2. By January 31st, 2021, cors-anywhere.herokuapp.com will stop serving as an open proxy. 3. From February 1st. 2021, cors-anywhere.herokuapp.com will only serve requests after the visitor has completed a challenge: The user (developer) must visit a page at cors-anywhere.herokuapp.com to temporarily unlock the demo for their browser. This allows developers to try out the functionality, to help with deciding on self-hosting or looking for alternatives. ### What should current users of CORS Anywhere do in response to this announcement? If possible, try to avoid the need for a proxy at all. CORS Anywhere works by combining proxy functionality with [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). You may not need proxy functionality, if the web service that you are trying to access already supports CORS. This is the preferred solution because it is faster and more reliable. For development, you can also consider the use of browser extensions that automatically enables CORS for certain websites. If your use of CORS Anywhere is infrequent, then the exception from step 3 above will allow you to continue as before. The only difference is that you need to explicitly opt in before access is temporarily allowed. If you'd like to not have these restrictions, then you should self-host CORS Anywhere. For an example of self-hosting, see https://github.com/Rob--W/cors-anywhere#demo-server . There are also many questions and answers about hosting on the issue tracker here (https://github.com/Rob--W/cors-anywhere/issues). If you have questions, please search for existing issues first before opening a new issue.

nmvega · September 8, 2022, 2:34am

It’s kind of off-topic on my part but, still bring new to Anvil, I hadn’t thought of applying Server Uplinks to arbitrarily stout backends in your own data center (or home) until @nickantonaccio mentioned that usage (I think he did - I’ll reread). Maybe in the back of my mind I did briefly imagine it (only because I used to design data centers with Sun & Solaris back in the day), but not really here. And the docs I think allude to this ability. I have to review the comment and docs because it opens up possibilities (not to be abused and there are security considerations, too), but just as an option to be aware of. Thanks.

nickantonaccio · September 8, 2022, 2:44am

This topic gets right to what I see at the beauty of the whole Anvil design: a built-in drag-drop GUI designer with full access to creating dynamic layouts in Python code and optional full access to HTML/CSS/JS to build front end interfaces, with some basic Python language functionality right there in the front end. The real benefit is the ability to connect so easily with the overwhelming majority of the real, full Python ecosystem in server modules, for anything that can’t be done in client code. Aside from the typical ‘web framework’ benefits (user management, database ORM, HTTP API endpoints, etc.), and lots of other built-ins (visual data table builder, Google, Stripe and other APIs, etc.), it’s the smooth integration between front end and that super powerful Python back end, just by putting functions in a module that lives on the server and passing native Python values as arguments. And if something can’t be loaded on Anvil servers, or if you want to control a robot, or a Pico W - or if you want to build your own data center backend - there’s uplink. And it’s all implemented so cleanly and professionally, with a built-in IDE with autocomplete, GIT integration, etc. … plus it’s all neatly hosted and there’s the open source server to offer some safety … jeez, it’s just so good

nmvega · September 8, 2022, 3:57pm

Yes. It was a combination of a comment that you made, alongside a comment that @jshaffstall made at around the same time (further up) concerning why an Anvil module wasn’t available in a Client or Server Uplink context:

As I wondered what he meant, coupled with your “servers in a data-center” comment, it dawned on me that Uplinks are gateways to entend processing power into arbitrary environments (with security, bandwidth and other concerns to account for, of course). How beautifully extensible, I thought.

Now, to be clear, I had read the Uplink docs before - I absolutely did - but their purpose & power didn’t render to me until comments in this thread helped me tie it together.

I guess it’s because one of my first experiences with Anvil (probably the first), was trying to setup development in the CLI using Uplinks, since I’m used to vim(1), the ptpython(1) REPL, etc; and so my concept of Uplinks was that use-case, and not the more general understanding that I now have.