Enum class with ToString functionality

[bg_ie]

Hi,

I have the following class -

class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

plus the following code -

testResult = TestOutcomes.PA SSED

testResultAsStr ing
if testResult == TestOutcomes.PA SSED:
testResultAsStr ing = "Passed"
elif testResult == TestOutcomes.FA ILED :
testResultAsStr ing = "Failed"
else:
testResultAsStr ing = "Aborted"

But it would be much nicer if I had a function to covert to string as
part of the TestOutcomes class. How would I implement this?

Thanks,

Barry

[Bruno Desthuilliers]

TheFlyingDutchm an a écrit :

On Sep 8, 9:52 am, Bruno Desthuilliers
<bdesth.quelque [e-mail] quepart.frwrote :

>>TheFlyingDutc hman a écrit :

(snip)

>>>class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

>> def ToString(outcom e):
if outcome == TestOutcomes.PA SSED:
return "Passed"
elif outcome == TestOutcomes.FA ILED :
return "Failed"
else:
return "Aborted"

>> ToString = staticmethod(To String)

(snip)

>>Technically correct, but totally unpythonic.

Speaking of unpythonic, I would call

ToString = staticmethod(To String)

A Perlific syntax.

Nope, just a good ole HOF.

But nowadays, it's usually written this way:

@staticmethod
def some_static_met hod():
pass

>

>>May I suggest some reading ?http://dirtsimple.org/2004/12/python-is-not-java.html

Well the Foo.Foo complaint is bogus:

from Foo import Foo

Yes. And properties are bogus - just use getters and setters.

Seriously, writing Java in Python is definitively on the masochist side.
But if you like pain...

[Zara]

On Mon, 10 Sep 2007 02:28:57 -0700, bg***@yahoo.com wrote:

>Hi,

I have the following class -

class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

plus the following code -

testResult = TestOutcomes.PA SSED

testResultAsSt ring
if testResult == TestOutcomes.PA SSED:
testResultAsStr ing = "Passed"
elif testResult == TestOutcomes.FA ILED :
testResultAsStr ing = "Failed"
else:
testResultAsStr ing = "Aborted"

But it would be much nicer if I had a function to covert to string as
part of the TestOutcomes class. How would I implement this?

You should implement __str__ (or __repr__) method in your class,

class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

def __str__(self):
textResultAsStr ing="Unknown"
if testResult == TestOutcomes.PA SSED:
testResultAsStr ing = "Passed"
elif testResult == TestOutcomes.FA ILED :
testResultAsStr ing = "Failed"
else:
testResultAsStr ing = "Aborted"
return testResultAsStr ing

Regards,

Zara

[Ben Finney]

TheFlyingDutchm an <zz******@aol.c omwrites:

On Sep 10, 7:55 pm, "J. Cliff Dyer" <[e-mail] tar.orgwrote:

Uh... The 1.0 version is vaporware?

I think not. 42% of it is alive and kicking as we speak.

That's odd. Do you think some similar matchematical relationship
exists between Python version 2.4.4 and 3.0?

You've made the common error of reading a package version as though it
were a single number on a number line. That's not the customary
semantic, though: versions are interpreted as a tuple of distinct
integers.

When you were developing your Enum module, how did you determine you
were at the 0.4.2 version as opposed to the 0.7.1 version or the
0.9.2 version?

I initially developed at version 0.0, meaning "major level 0, minor
level 0" — i.e., no releases at all.

Then, when the first "alpha" release was ready, I called it version
0.1, meaning "major level 0, minor level 1" — i.e. no major releases
yet, but the first minor release.

Then, a small patch needed to be made, and the resulting release was
version 0.1.1, meaning "major level 0, minor level 1, patch level 1" —
i.e. the first patch to version 0.1.

Eventually some extra features warranted a release of version 0.2,
meaning "major level 0, minor level 2" — i.e. the second minor release
with still no major releases. Implicit in this is "patch level 0",
i.e. no patch-level versions yet; the version could be called 0.2.0
and have the same meaning.

Each dot-separated integer is interpreted as a distinct level,
subordinate to the preceding one:

* Two versions with different major numbers can be expected to be
incompatible.

* If two versions have the same major number, one can expect only
minor feature differences.

* If two versions have the same major and minor number, one can
expect that they differ only in bug fixes or the like.

* Subsequent integers would imply even smaller differences at that
same level if all preceding numbers were the same.

Within a level, subsequent integers imply subsequent release times:
version 0.4.1 can only be released before 0.4.2. However, this is not
true across levels: a hypothetical version 0.2.7 could be released
before *or* after 0.4.2, if the author decides a patch to the (equally
hypothetical) version 0.2.6 is warranted.

As for a putative version 1.0, that will not be released until I
determine the package is functionally complete and warrants a first
major release. Depending on how much changes between now and then, it
may have most, some, or none of the code you see presently in version
0.4.2.

--
\ "That's all very good in practice, but how does it work in |
`\ *theory*?" —Anonymous |
_o__) |
Ben Finney

[J. Cliff Dyer]

Zara wrote:

On Mon, 10 Sep 2007 02:28:57 -0700, bg***@yahoo.com wrote:

>Hi,

I have the following class -

class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

plus the following code -

testResult = TestOutcomes.PA SSED

testResultAsSt ring
if testResult == TestOutcomes.PA SSED:
testResultAsStr ing = "Passed"
elif testResult == TestOutcomes.FA ILED :
testResultAsStr ing = "Failed"
else:
testResultAsStr ing = "Aborted"

But it would be much nicer if I had a function to covert to string as
part of the TestOutcomes class. How would I implement this?

You should implement __str__ (or __repr__) method in your class,

class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

def __str__(self):
textResultAsStr ing="Unknown"
if testResult == TestOutcomes.PA SSED:
testResultAsStr ing = "Passed"
elif testResult == TestOutcomes.FA ILED :
testResultAsStr ing = "Failed"
else:
testResultAsStr ing = "Aborted"
return testResultAsStr ing

Regards,

Zara

This code cannot output "Unknown," because you use an else: at the end
of your if-chain to represent a specific (non-catch-all) case.

s/else:/elif testResult == TestOutcomes.AB ORTED:/

Cheers,
Cliff

[Scott David Daniels]

bg***@yahoo.com wrote:

Hi,

I have the following class -

class TestOutcomes:
PASSED = 0
FAILED = 1
ABORTED = 2

plus the following code -

testResult = TestOutcomes.PA SSED

testResultAsStr ing
if testResult == TestOutcomes.PA SSED:
testResultAsStr ing = "Passed"
elif testResult == TestOutcomes.FA ILED :
testResultAsStr ing = "Failed"
else:
testResultAsStr ing = "Aborted"

But it would be much nicer if I had a function to covert to string as
part of the TestOutcomes class. How would I implement this?

Thanks,

Barry

class Outcome(object) :
PASSED, FAILED, ABORTED = range(3)

@classmethod
def named(class_, value):
for name in dir(class_):
if name[0] != '_' and getattr(class_, name) == value:
return name
raise ValueError('Unk nown value %r' % value)

Outcome.named(2 )
-Scott David Daniels
Sc***********@A cm.Org

[Neil Cerutti]

On 2007-09-11, Steven D'Aprano <st***@REMOVE-THIS-cybersource.com .auwrote:

Perhaps Ben should have followed the usual practice of
commercial, closed- source software developers and started
counting his version numbers at one instead of zero, miss a few
releases, use randomly large increments occasionally, and ended
up with a current version number of 2.7.1 for the exact same
level of functionality.

Or he could have called it "Enum XP" (for "eXtra Programming"
perhaps) or "Enum 2007". The next minor release could be "Enum
2008", and the next major update could be called "Enum
Professional Capowie!!!".

I like the (priviledged) code names adopted by the Linux
community for special versions, e.g., Enum 2.7.1 (Flapjacks).
This would really tie the Enum-using community together, and make
messages about it much cuter.

--
Neil Cerutti