Allow paths for top namespace

[ryaminal]

Description

Adding the forward slash / to the filter for top-namespace when normalizing

Motivation and Context

We would like to create a top level with something like foo/bar so that the module can be imported as import foo.bar.stuff.

How Has This Been Tested?

Tested this locally on my mac. Should work on most *nix systems, but I'm not certain how it will impact Windows. Made sure to have files that actually import with the top-namespace.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [X] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [X] I have read the code of conduct.
• [X] I have read the contributing guide.
• [X] I have updated the documentation accordingly (if applicable).

[ryaminal]

I was really struggling to figure out how to better test this so mistakes like I made in #32 don't happen again. A simple unit test isn't sufficient, it seems. I wonder how the Poetry project and other Poetry plugins do unit/integration tests? We could do essentially automate what I started to do to test:

1. create poetry project
2. create a few files
3. create another project that will consume project 1
4. build project 1
5. install project 1 in to project 2

6. run a pytest in there

   That is so very cumbersome to setup, but not the end of the world. Curious if there is a better way for another PR.

[DavidVujic]

Thank you @ryaminal, I'll have a look!

[ryaminal]

We started using a project published with these changes and it appears to be working. Apologies again for the wasted time with my mistakes.

[DavidVujic]

Great, thank you @ryaminal! ⭐ I will have a look this weekend.

[DavidVujic]

v1.30 is out! Thank you for contributing to this project!