generated package's version

[halfAPI]

What happened:

I depend on an hop-generated package in my project. I updated the python code of the generated classes, and would like to refer to the specific version of this package in my project.

Need

As we tend to add code to the package's generated python files after patching, these modifications would also need to be included into release version.

We can't force the user to create a new patch and a new release each time he wants to publish it's generated package.

Usually, the modifications done in the python files will need a certain version of the patched library. So it's normal that a "Patch" operation is the release leader, so the additions to package code should follow.

Pep

In PEP440, the post release may be used only for minor modifications that don't affect the software itself (like changelog, doc...). If we follow this PEP, we would be leaded to use the last part of the version to specify the release version between patches. We then would have to remove a level of deepness of "Patches" tree, so we would have only major.minor patches version.

Suggestion

i.e:

tree Patches
Patches/
└── 4
    ├── 0
    │   ├── CHANGELOG.md
    │   └── test.sql
    ├── 1
    │   ├── test.sql
    │   └── CHANGELOG.md
    └── 2
        ├── CHANGELOG.md
        └── test.sql

commit log :

4.0.0 - hop patch
4.0.1 - added foo function to proj/test.py
4.0.0 - hop patch
4.0.2 - added bar function to proj/test.py
4.0.3 - added foobar function to proj/test.py
4.0.4 - hop patch

What do you think about that?