No problems using similar UK services for EU citizens I know, nor non-EU. Usual bank/address shenanigans at the start, but no issues with government gateway etc.

Not sure if that was added later.

I thought SR-71 had some strike capabilities, but I could be mistaken.

"In order to get all of the details about the tuple from the function one must analyse the bytecode of the function. This is because the first bytecode in the function literally translates into the tuple argument being unpacked. Assuming the tuple parameter is named .1 and is expected to unpack to variables spam and monty (meaning it is the tuple (spam, monty)), the first bytecode in the function will be for the statement spam, monty = .1. This means that to know all of the details of the tuple parameter one must look at the initial bytecode of the function to detect tuple unpacking for parameters formatted as \.\d+ and deduce any and all information about the expected argument. Bytecode analysis is how the inspect.getargspec function is able to provide information on tuple parameters. This is not easy to do and is burdensome on introspection tools as they must know how Python bytecode works (an otherwise unneeded burden as all other types of parameters do not require knowledge of Python bytecode).

The difficulty of analysing bytecode not withstanding, there is another issue with the dependency on using Python bytecode. IronPython [3] does not use Python's bytecode. Because it is based on the .NET framework it instead stores MSIL [4] in func_code.co_code attribute of the function. This fact prevents the inspect.getargspec function from working when run under IronPython. It is unknown whether other Python implementations are affected but is reasonable to assume if the implementation is not just a re-implementation of the Python virtual machine."

I'm not very convinced without further information - it sounds like it was already solved in CPython, and bug in IronPython? The whole PEP reads as if it's looking for excuses for removal.

I find this especially annoying for lambdas.

In fact, now also I get some places trying to be too helpful to the point of being confusing. For example, a trainer store that auto-detects location and lists prices in GBP but sizes in US (without indication) and doesn't actually have an EU/UK distribution centre. So whoops it's going to take ages to arrive, it gets re-listed in USD at the final checkout, whoops again, 3% charge from my credit card, and then the wrong size arrives. But at least I knew the rough GBP amount!

My point is, there is quite an involved pricing model - 5 tiers, each tier has multiple charges in it, none of them obviously correspond to the advertising on the front page. They even repeatedly use the phrase "for X MB" which is unclear to me. I first read it as storage. I assume it means total upload/download? The numbers for this on other devices on the front page are not mentioned on the pricing page. Charging categories also have a mixture of sold-by-the-MB and sold-by-usage, as well as pre-sold - within a single tier.

The front page is selling "look, it's very clear and simple" and it's just obviously not clear and simple. Unclear why that view garners downvotes - this is honest feedback about their marketing and pricing. Even if they are mostly talking about the free tier, it's not clear