I cannot answer to your input in here, but I got it sorted now.
It is as you say, but renaming the original file is not enough.
You have to delete the *.pyc file too. I only renamed the the offendingt
filename and since it did not work I searched for other options.
This was tricky because the errormessage was missleading.
Anyway. I have sort it out now.
Thanks for your input.
This is it, normaly when you code you often type out the filename
to what you are about to code, for example: Hello World.
So the filename is named helloworld.py
And in this spirit of nameconvention I named my Pythonfile
sqlite3.py
I had no idea that decision would give me so much grief
I wrote the appropriate code and couldn't for some reason get passed the error
No Module found Error: sqlite3
This clearly tells me that, for some reason I don't have that module.
Anyway, using pip command freeze, is going to sort this out.
Strangely enough, no module in the list with sqlite3. That send me on a wildgoose-chase.
Apparantly I am missig this module.
That's strange since I have a Python ver. 3.8.2
and it is equipped with an build-in sqlite3 module.
But I could not verify it.
I searched everywhere, and all suggestions I found was leaning towards that
something was missing in my Pythoninstallation. I'll tried everything. To no avail.
Then after some 2-3 days of research. I found this thread.
It said that Python cannot distinguish between a modulename or a filename,
if they are having exactly the same names.
By following the solution here. So easy.
Save your sqlite3.py file as a new filename, something different.
then find your Python cache-file named *.pyc, delete the *.pyc file.
Now everything works.
So even if the module sqlite3 did not get listed via pip freeze command it
was apparently there the whole time build-in to another module.
Note that I did not reinstall anything or added other modules to get this to work.
Just renamed the py-filename or saved under a different name and
deleted the *.pyc file. No other alternations.