EOL is a clearly defined term and its date has also been set for ages now.
Just because something has gone EOL doesn't mean it's no longer in use though. To make the most obvious example: Every company i've ever worked for used servers for years and even decade(s) after the EOL date had passed.
Facebook is migrating everything. The Instagram migration in particular got quite a bit of press coverage due to the PyCon keynote.
Other organizations may choose to not rewrite or migrate. At their own peril. Likely a third party like RedHat will continue patching 2.7 for their customers but no Python.org releases will be done anymore.
More importantly, after 2.7 EOL library maintainers will drop support like it's hot. And that no single player will be able to continue supporting.
So, you might get a few more years out of 2.7 but it will be an increasingly frustrating and insecure experience.
That's a website that lets you create countdowns. It's not affiliated to Python.
But yes, I guess you could convince some company to keep supporting Python 2 for you. In fact it would surprise me if such service doesn't pop up just before Python 2 support ends. May be much cheaper than porting to 3 for some companies.
This seems to be only a WebKit issue, you can produce the same results on desktop Safari. Other browser engines must detect when an alpha channel value is used with an `rgb` CSS attribute and update that attribute to `rgba` accordingly as an assumed fix.
