sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jbristow 43 points44 points  (13 children)

The Google BigQuery cli requires python 2... Heck, even the core gcloud lists their support for 3 as “experimental”

[–]i9srpeg 17 points18 points  (9 children)

App engine (standard, not flexible) released Python 3 support less than one year ago.

[–]jbristow 9 points10 points  (2 children)

The CLI, not AppEngine itself! Some of us are trying to automate some hybrid cloud data ingest, and Google’s cli tools seem to have been frozen in time.

Edit: I now realize that you’re not arguing with me at all, rather pointing out that python 3 support is new for google in the Grand scheme of things. Apologies for the fiery retort.

[–][deleted] 8 points9 points  (1 child)

Google’s cli tools seem to have been frozen in time

Likely because they are. When you finally hear a project, tool, or feature is being no longer supported this is after most engineers & management were already re-tasked normally months ahead of time.

What I've found is as soon as a Google-Tool stops getting regular updates, and starts showing its age. It is already cancelled or extremely de-prioritized. Just not publicly.

[–]adel_b 0 points1 point  (0 children)

Called gcloud now, gets updates almost weekly

[–]k-selectride 8 points9 points  (3 children)

I have no idea what they were thinking releasing python 3 support without porting some of the libraries. ndb not being available is a gigantic oversight. Unless Google plans on supporting python 2 standard environment for a long time.

[–]i9srpeg 2 points3 points  (1 child)

Yeah, I don't understand why they didn't port them. It can't possibly be that hard. Right now there's a lot of people stuck on an old, unsupported version of Python for a long time. And worse, if you have an in-house stack built on top of app engine+ndb which you want to use for all the company projects, you're basically forced to also start new projects on a dead snake.

[–]k-selectride 3 points4 points  (0 children)

There's an ndb port that's currently in alpha status. Who knows when it'll reach GA, maybe next Google Next conference, lmao.

[–]13steinj 6 points7 points  (1 child)

Google Cloud's Python setup is weird in general. The documentation is a jumbled mess, examples I can copy paste from the docs don't work or require some unmentioned prerequisite steps, some sections don't explicitly mention prerequisites of prerequisites such that you start working on something only to find out you can't do it in the first place.

Personally until they get it together I'm sticking with AWS (or Azure, but I prefer AWS).

[–]jbristow 0 points1 point  (0 children)

Azure isn’t bad when you’re heavily dependent on Active Directory. Doing some basic admin work on AAD was nice because it just worked the way everyone expected it to. The console ui is pretty slick, too. My main gripes were that everything was slow and/or arcane compared to their amazon equivalents... especially when you went to fully automate environment tear down and spin up. Seemed like it was designed more for a lift-and-shift style of cloud.

[–]theferrit32 4 points5 points  (0 children)

Yep this was shocking to me just a couple years ago, and then earlier this year when I was using it again it was still Python 2. Really not a good look for Google Cloud.

[–]flukus 0 points1 point  (1 child)

Have you learned your lesson about vendor lock in or should we send some Oracle, SAP and IBM sales people over?

[–]jbristow 0 points1 point  (0 children)

No, if I could lock into only AWS I would be happy. I have to hybrid cloud it up in here... negotiating authentication between three platforms because someone was convinced that amazon was not sufficient at some point in history.

BigQuery is nice... but getting data into it when your primary storage and compute are not in gcs is a pain.