1 + f in modern Python results in a ValueError.
709 karma · joined November 16, 2014
1 + f in modern Python results in a ValueError.
Not the case. For the walkie talkie it was evaluated and the design (including location and it's orientation) were passed by a consultancy for a bunch of environmental items.
Seemingly that wasn't the case and they spent £13m retrofitting shutters. AFAIK the main contractor went after the consultancy for the money but I can't for the life of me find any references right now.
And SIS/GCHQ wonder why they have such a hard time recruiting staff.
Python even has limited generics now through mypy and pep 484.
I find merino wool to be far the best base layer. It's fantastic at wicking and doesn't smell at all.
Royal family costs the UK £307m (highest number) with a revenue from them of £500m [1]. Seems like good business to keep paying for them.
1. https://www.theatlantic.com/international/archive/2013/07/is...
A minority voted to leave the EU.
That's not really true anymore. Wind power supplies double that of coal in the UK. It's gas, nuclear and wind with coal coming in 4th. Check out http://www.gridwatch.templar.co.uk/ for live figures.
You also have to think about when they will be consuming electricity, which will primarily be at night (taking a reasonable guess here) where the balance of wind and nuclear is even higher.
Agreed, but wasn't this also an issue with steel windows in the 60s? uPVC put in in the early 90s already looks crap (IMO).
Hugely, I think it's a testament to the design that they still look great today. Double glazed wooden sash windows are however much pricier than a uPVC alternative which puts them out of reach of many.
I'm not sure where you got the gripe against wood from. It lasts longer than uPVC given maintenance every 5 years, looks better, is more environmentally friendly and has similar thermal properties. Oh and it doesn't go yellow.
Honestly though I can't say I've ever really needed support on GCP, most of the times I've raised tickets its been due to funny behaviour (slow spinning disks in us-central1 was the last one).
Er, that's a bet I'd strongly suggest you didn't make.
Not ideal but it's better than pure X vs Y.
Not strictly true, http://doc.pypy.org/en/latest/stm.html. In general for the main project however, this is true.
Python 2.7 is what's running at Google. Not really surprising they're looking at this considering the fast approaching end of (core dev) support for Python 2.7.
Write an interpreter in another language and programatically port modules to Go. Seems pretty sensible to me.
virtualenvs don't create a new interpreter, they just fudge the python path?
Definitely not recommended on interpreted languages (although we use it all the time on our go apps).
2 different people watching high definition video at a high bit rate.