Unless I'm crazy, we still do. These guides differ from the internal guides in various strange ways.
I'm pretty sure these are the coding standards for code released outside of Google. For various disgusting historical reasons Python written internally spits in the face of PEP8 naming conventions. (And other weird niggles.)
There is a Google-specific guide. Its mostly of the form "go read the Sun style guide", with some specific clarifications of things the Sun style guide is quiet on.
The C++ guide interestingly recommends not using a number of language features (exceptions for instance) and advises a more standard-like approach on Windows. I wonder what seasoned windows programmers make of it http://google-styleguide.googlecode.com/svn/trunk/cppguide.x...
I was reading that the worst problem of C++ is to decide what 10% of the language to use in your project. Google is trying to do this to avoid such conflicts.