Linux Format forums

Re: RE: Re: RE: Python module version types.

Lejon — Mon Oct 24, 2005 1:32 pm

Author: Lejon

Posted: Mon Oct 24, 2005 1:32 pm

overflow wrote:

Our version numbers are inserted by CVS so it has to be strings.

Dose not "has to be".
As you can easy create a function that can return it as a tuple.
However I see your point.

RE: Re: RE: Python module version types.

overflow — Mon Oct 24, 2005 1:29 pm

Author: overflow

Posted: Mon Oct 24, 2005 1:29 pm

Our version numbers are inserted by CVS so it has to be strings.

Re: RE: Python module version types.

Lejon — Mon Oct 24, 2005 9:21 am

Author: Lejon

Posted: Mon Oct 24, 2005 9:21 am

M-Saunders wrote:

Corrected

M

Thanx

Now if people only could start to vote!
Am I the only python dev here? I know I am not alone!

RE: Python module version types.

M-Saunders — Mon Oct 24, 2005 9:17 am

Author: M-Saunders

Posted: Mon Oct 24, 2005 9:17 am

Corrected

M

Python module version types.

Lejon — Sat Oct 22, 2005 10:16 pm

Author: Lejon

Posted: Sat Oct 22, 2005 10:16 pm

The 2 most common types for module versions seams to be
string (eg. 1.2.3) and tuple (eg. (1, 2, 3)).

Witch of thes two do you prefer?

My thoughts.
The String one can ofcourse be printed easaly for a report.
While the tuple is easyer for advanced compair.
And I find it easyer/faster to convert from tuple to string, than from string to tuple.

Do'h, cant Edit the Pool question.
Ofcourse it is ment to be "do..." not "fo..."