Has Google just made getting credentials.json more tedious?

[Clement-Lelievre]

A few months back, I implemented the procedure described in the README and it worked perfectly, in particular as regards the way to obtain credentials.json and token.json.
Now coming back to it and going through the whole thing again, I visited https://developers.google.com/gmail/api/quickstart/python as per the README but the 'Enable the Gmail API' button was, this time, nowhere to be found.
After some research, I still managed to get a proper account and to finally send email with Python, but only through non trivial trials in the Google Cloud Console, setting up a project, then Oauth etc.

So, unless I missed a simpler way to proceed, which is possible, is it time to update the README in order to adjust to this fresh, harder Google account setup?

[elliotkantor]

Yeah, Google definitely changed this since reading Automate the Boring Stuff. I made these changes to the readme in PR #34

[micjgam]

So... I just went through this rigamarole as well with GCP. In the end, I was able to generate the credentials.json file and the subsequent token.json.

However, now I am getting a KeyError: '_module' error when calling ezgmail.init(). I have the prerequisite modules and files already. All solutions say to delete the token.json file and rerun the authorization process, but this does not work.

Any other solutions out there?

Here is the traceback:

      File "<stdin>", line 1, in <module>
      File "c:\Installs\Python\lib\site-packages\ezgmail\__init__.py", line 471, in init
         creds = store.get()
      File "c:\Installs\Python\lib\site-packages\oauth2client\client.py", line 407, in get
         return self.locked_get()
      File "c:\Installs\Python\lib\site-packages\oauth2client\file.py", line 54, in locked_get
         credentials = client.Credentials.new_from_json(content)
      File "c:\Installs\Python\lib\site-packages\oauth2client\client.py", line 302, in new_from_json
         module_name = data['_module']
  KeyError: '_module'

*** UPDATE ***

I changed a line in the ezgmail/init.py file (line 471) from:

      creds = store.get()

to:

     creds = None

Immediately upon running

     import ezgmail

apparently a new token.json file is written. I then reverted the ezgmail/init.py file (line 471) back to...

     creds = store.get()

... and now I can run ezgmail.init() with no issues!

This represents my limited knowledge of python and I am only just beginning, so please bear with my explanation above.

[chernoar]

I find myself having to reauthenticate once every week or so (GMail opens the browser, asks for permissions and then generates a verification code to paste in the console).

I'm reading things about refresh tokens which can be obtained.
Did anyone figure out a more permanent solution compatible with EZGmail?

[asweigart]

Yes, the process is much more tedious now, but I've written out all the steps in the README. I'm looking into how to make this easier to do in the future.