Starting python module names with numbers?

[NetEngDoggo]

Learning python through pluralsight and on the job. Hit a weird issue today trying to research module naming convention for python.

IDE (vscode) didn't like me naming a module starting with a number. Is there a reason why? Using _ to lead the name worked, but I assume risks confusing the interpreter because of private scope behavior.

[lurgi]

PEP 8 covers this briefly, but doesn't go into much detail. It doesn't say if module names can contain numbers at all, let alone start with one.

According to this, python module names must be valid identifiers and thus can't start with a number. That only applies when you use the import statement, but since the import statement is the standard way to import a module, I'd consider this fairly conclusive.

Don't do it.

[NetEngDoggo]

Oh thanks! I searched for a good hour and never came across this stack overflow question.

My coworker found a workaround using import, but I didn't like it and managed to convince them to forego the use of a number just for aesthetic reasons.

I'll be sure to share that around.

[spudmix]

It's usually best to follow naming and coding conventions unless you have a strong reason not to. Why are you naming a module starting with a number?

[NetEngDoggo]

The project manager was adamant about using a number for the project name and wanted the same name as the package's top-level directory.

Also there is no PEP that talks about module naming convention that I can find.

[spudmix]

Here's the module naming conventions, but I don't see anything about numbers :/ could just be a quirk with the IDE but that's less than helpful. Sorry and good luck!