thegooglecodearchive / pydicom

Automatically exported from code.google.com/p/pydicom
0 stars 0 forks source link

pydicom lacks embedded version infoformation #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Many (most?) Python modules have embedded version info; pydicom does not. When 
writing install routines, it's really nice to be able to import a module and 
check that the version is adequate. For example -- 

>>> import dicom
>>> dicom.__version__
'0.9.4'

There's no official standard for the name of this attribute, but the Python 
world seems to be coalescing around __version__. See here for more info:
http://stackoverflow.com/questions/458550/standard-way-to-embed-version-into-pyt
hon-package

I'd like to see this simple feature added to pydicom.

Thanks
Philip

Original issue reported on code.google.com by NikitaTh...@gmail.com on 11 Jun 2010 at 4:24

GoogleCodeExporter commented 9 years ago
dicom.__version__ was added a while ago -- it should be available in recent 
versions  (it is working for me on my 0.9.4-1 version). 

I like the idea of also having the tuple __version_info__ as discussed in that 
link; I'll leave this issue on to add that. I'm not sure what people do with 
__version__ or __version_info__ for repository revisions between releases, 
though ... any idea on that? The linked discussion talks about embedding 
revision numbers from the source control system, but I'm not a fan of doing 
that.

Original comment by darcymason@gmail.com on 14 Jun 2010 at 2:57

GoogleCodeExporter commented 9 years ago
Sorry, I'm still on 0.9.3 and I didn't see anything in the issue tracker 
related to __version__. Thanks for adding it.

I don't know if there's a standard for inter-release numbers. Adding a 'b' for 
beta might work, as in "0.9.4b".

Original comment by NikitaTh...@gmail.com on 14 Jun 2010 at 2:57

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 63ab240c0c.

Original comment by darcymason@gmail.com on 28 Jul 2010 at 11:47