pytoml | python serializer/deserializer for toml | Parser library

I'm experimenting with GCP's cloud functions and python for the first time and wanted to get python's logging integrated sufficiently so that they fit well with GCP's logging infrastructure (specifically so that severity levels are recognized, and ideally execution_ids and trace ids also are included.

I've been following https://cloud.google.com/logging/docs/setup/python to get this set up.

My code:

I did the setup for using the Google Vision API via Python, but it doesn't work and I don't find any good solutions. No matter what I do, I always get "AttributeError: module 'google.cloud.vision' has no attribute 'types'"...

Here is an example Code I use (Authentication etc. is done).

For getting the list of installed libraries, I run the following command in Jupyter Notebook:

My OS is ubuntu 20.04 and my default python is 3.8.2. I'm trying to create a virtual environment with pipenv and python 3.7. The following error occurs when I run pipenv install --python 3.7:

I'm getting this error while executing the command buildozer android release while building apk for Kivy app. I'm using Python 3.7.4 and still it shows the same.

UPDATED:

Command: buildozer android debug

I am trying to install Python's cryptacular package but keep running into an error:

Without sudo:

I am new in python and would like to learn web scraping with python. My first project are the yellow pages in Germany.

When executing my code, I am getting following IndexError after scraping 12 pages:

('Traceback (most recent call last): File "C:/Users/Zorro/PycharmProjects/scraping/venv/Lib/site-packages/pip-19.0.3-py3.6.egg/pip/_vendor/pytoml/test.py", line 25, in city = city_container[0].text.strip() IndexError: list index out of range

Process finished with exit code 1')

I would like to know how I can skip this error, so that python does not stop scraping.

I tried to use try and except blocks, but did not succeed.

I'm trying to define a coding standard for a project and I want to specify use of JSON Schema version 4.

However, from the offical JSON Schema website, if you follow the links for the Specifications, takes you to the github page, then into the Version 4 Draft at the IETF. This document explicitly states that it is an Internet-Draft document and says:

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

Since there don't seem to be any versions of the JSON Schema that are anything other than Internet-Draft status, how should I reference this?

Edit: This is in a written project document, not within a JSON file itself. I currently have text like this:

Python Standards and Style
- All Python Source Files MUST be written in Python 3.x, specifically targeting Python 3.5.1 as the default Python 3 installation with Ubuntu 16.04 LTS.
- All Python Source Files MUST conform to the PEP 8 standard [footnote: https://www.python.org/dev/peps/pep-0008/ ].
- All Python Source Files MUST pass a flake8 [footnote: https://pypi.python.org/pypi/flake8/3.2.1 ] check before each delivery. The checker MUST be set up to be ultra-pedantic and it MUST be considered a unit test failure if the checker needs to change anything on the checked in Source Files.
- All Python Source Files SHOULD use Docstrings conforming to the PEP 257 standard [footnote: https://www.python.org/dev/peps/pep-0257/ ].
JSON Standards and Style
- All JSON Source Files MUST be written in JSON Schema version 4 [footnote: https://tools.ietf.org/html/draft-zyp-json-schema-04 ].
- All JSON Source Files MUST conform to the Google JSON Style Guide 0.9 [footnote: https://google.github.io/styleguide/jsoncstyleguide.xml ]
- All JSON Source Files MUST pass a jsonschema [footnote: https://python-jsonschema.readthedocs.io/en ] check before each delivery. The checker MUST be set up to be ultra-pedantic and it MUST be considered a unit test failure if the checker needs to change anything on the checked in Source Files.
TOML Standards and Style
- All TOML Source Files MUST adhere to v0.4.0 of the TOML standard [footnote: https://github.com/toml-lang/toml ].
- All TOML Source Files MUST be loadable with the pytoml parser v0.1.11 [footnote: https://github.com/bryant/pytoml ], without error.
- All TOML Source Files SHOULD be aligned at the left margin – i.e. do not indent sub-sections.

To me, the italicised footnote to the JSON Schema reference would count as citing an Internet-Draft document, which is explicitly stated as not appropriate in the excerpt I gave above.