Closed glemaitre closed 6 years ago
you might want to consider to start your versioning at 0.1.0 since that you don't have a major revision. But I let you as you want since that there is not strong enforcement regarding the versioning
My plan is to use the major version as the file format, the minor when there are API changes, and the revisions for... revisions (what a surprise!).
As a matter of fact, I have files which were created by an unreleased version of mmappickle
, which are of version 0.
I plan to do a 1.0.1 release when all the issues are fixed.
Ok good for me :)
On 24 April 2018 at 12:41, Laurent Fasnacht notifications@github.com wrote:
My plan is to use the major version as the file format, the minor when there are API changes, and the revisions for... revisions (what a surprise!).
As a matter of fact, I have files which were created by an unreleased version of mmappickle, which are of version 0.
I plan to do a 1.0.1 release when all the issues are fixed.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/UniNE-CHYN/mmappickle/issues/5#issuecomment-383886301, or mute the thread https://github.com/notifications/unsubscribe-auth/AHG9P0QpiVfFPO9dl7xCQHaBfWWDYZviks5trwE-gaJpZM4TgLr7 .
-- Guillaume Lemaitre INRIA Saclay - Parietal team Center for Data Science Paris-Saclay https://glemaitre.github.io/
There is no variable
__version__
accessible which is usually something quite standard. You should create a_version.py
module in which you define the version and import it in__init__.py
You can read_version.py
inside thesetup.py
to not have to import directly.Basically I am expecting something like: