Message13098

Author doublep
Recipients doublep
Date 2020-06-04.12:29:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591273744.38.0.236096943499.issue2898@roundup.psfhosted.org>
In-reply-to
Content
Recently our application upgraded from Jython 2.5 to 2.7.2. As a side effect, all previously stored serialization representations (e.g. of PyList) became unreadable. This is caused by internal change in representation of various Jython objects. Note that using 'pickle' in our case is not an option, because we are serializing Java objects that _sometimes_ also include Jython objects, but Jython is not the main target.

However, additionally Jython classes lack 'serialVersionUID' field. Which means that even changes that are serialization-compatible in principle could lead to accidental change of autocomputed UID value and thus break unserialization of older representations.

Please add 'serialVersionUID' to serializable classes (initializing it to the current autocomputed value). Also, please weigh serialization compatibility against other reasons if considering changing internal object structure again.
History
Date User Action Args
2020-06-04 12:29:04doublepsetrecipients: + doublep
2020-06-04 12:29:04doublepsetmessageid: <1591273744.38.0.236096943499.issue2898@roundup.psfhosted.org>
2020-06-04 12:29:04doubleplinkissue2898 messages
2020-06-04 12:29:04doublepcreate