I vote for getting rid of the "L" everywhere. It has caused me some problems and extra fmt attributes in my DTML, too.

In the stock Zope 1.10.2 distro, putting a Long in a property causes a curious error to manifest. When the property page is displayed, the long is display like 44353L. If the then change any other property and attempt to save changes, you get a traceback saying that the property for the long is invalid. You are forced to manually remove the 'L' before saving changes.

May I suggest that when the properties are display, if the type is 'long' then the display code should do something like this: str(long_value)[:-1]

This would remove the L before it was ever displayed.... Alternatively, something in the response code needs to be modified to accept an 'L' at the end of an integer destined for a property whose type is 'L'.

Phil A ------------------------------------------ Philip Aylesworth zopelist@regalint.com Regal International