#1316 Update packaging-projects.rst with a tip on good module naming

source/discussions/choosing-a-module-name.rst

@@ -0,0 +1,32 @@
+Choosing a Module Name
+=========================
+
+This discussion is a complement to :doc:`/tutorials/packaging-projects`.
+
+Make sure to have a valid :ref:`Python identifier <python:identifiers>` for your module name.
+The PyPI project/dist name and the Python module may differ slightly.
+For example, your package in pyproject.toml and on PyPI may have the name abcd-1234.
+But a module named abcd-1234 would be cumbersome to import in Python,
+since it isn't a valid identifier.
+(There is a way to import it anyway, see :doc:`importlib <python:library/importlib>` and this question_.)
+
+.. code-block:: python
+
+   >>> import abcd-1234
+   >>> from abcd-1234 import something
+
+would not work.
+But having a directory structure with src/abcd_1234/ instead of src/abcd-1234/ has 2 consequences:
+
+- The following works:
+
+  .. code-block:: python
+
+     >>> import abcd_1234
+     >>> from abcd_1234 import something
+
+- Hatch will recognize that the module corresponding to the package is abcd_1234 instead of defaulting to src and building a not working wheel.
+
+More information about :doc:`Python imports <python:reference/import>` and its :doc:`grammar <python:reference/grammar>`.
+
+.. _question: https://stackoverflow.com/questions/8350853/how-to-import-module-when-module-name-has-a-dash-or-hyphen-in-it

source/discussions/index.rst

@@ -14,3 +14,4 @@ specific topic. If you're just trying to get stuff done, see
    wheel-vs-egg
    src-layout-vs-flat-layout
    setup-py-deprecated
+   choosing-a-module-name

source/tutorials/packaging-projects.rst

@@ -537,7 +537,7 @@ some things you can do:
   :ref:`pdm`, and :ref:`poetry`.
 * Read :pep:`517` and :pep:`518` for background and details on build tool configuration.
 * Read about :doc:`/guides/packaging-binary-extensions`.
-
+* Read about :doc:`/discussions/choosing-a-module-name`.
 
 ----