Maintaining Library Name Consistency Amid PyPi Deprecation Notice

[parth390]

Describe the bug
We got a deprecation notice from PyPi related to our library msci.sdk.

Our library msci.sdk is generating wheel file from the same name and according to the new validations or the rules set by PyPi we are getting deprecation mail related to this. It is recommended to update the name to msci_sdk from msci.sdk.

We tried changing this name in our side and also tried them on testPyPi which worked fine for the wheel file generation but our library name is getting changed as well due to which the user will also face some issues while pip installing the library as in this case it is no longer msci.sdk but is msci_sdk.

Is there a way where we can counter this deprecation issue as well as we can keep the previous name of the library?

Expected behavior
Resolving PyPi deprecation notice while keeping library name as msci.sdk.

To Reproduce
Got to library https://pypi.org/project/msci.sdk/ and check project description on landing page.
TestPyPi link where we made our changes - https://test.pypi.org/project/msci-sdk/1.20.0rc11/

My Platform

Additional context

[di]

The email you received explains how to resolve this:

In most cases, this can be resolved by upgrading the version of your build tooling to a later version that fully supports the specification and produces compliant filenames.

I can't see any source repository for this package, so I can't determine the details of how you're building it, but looking at the wheel you published, it uses version 0.40.0 of the wheel library which is several years old at this point. It's likely that you're using an outdated version of setuptools as well. Upgrading these prior to building the wheel should resolve this without needing to change the library name.

If you can provide more details on how you're building the wheel and how it is configured, that would be helpful here.