Hi,
I have no intent to officially support Python 2.3 and am quite surprised
that there is only one line that makes it incompatible ;-)
I'm keen to include a patch to make it compatible with 2.3 again (could
you provide that patch please?) but can't ensure that I won't introduce
any other incompatibility over time.
If you want to be safe make it dependent on Python 2.4 or higher.
BTW I'm about to release s3cmd 0.9.4 with all your updates as soon as we
solve all these problems (please use SVN version for your tests).
Michal
Mikhail Gusarov wrote:
tags 432705 upstream
thanks
Michal, I'm quoting full mail FYI. Do you want to use more 2.4 features or to
stay with 2.3 and decorator was used accidentally in this case?
Twas brillig at 17:20:57 10.07.2007 UTC-05 when Eric Evans did gyre and gimble:
EE> Line 68 of S3/S3Uri.py contains an instance of the new decorator syntax
EE> introduced in Python 2.4.
EE> @staticmethod
EE> def compose_uri(bucket, object = ""):
EE> return "s3://%s/%s" % (bucket, object)
EE> You'd have to go back as far as Sarge to find a release that contains a
EE> Python version older than 2.4, but there are bound to be quite a few people
EE> who've upgraded from older releases and still have python2.3 installed. As
EE> it stands now, byte-compilation fails and the package is left in an
EE> unusable state when an older Python version is installed.
EE> Please version your Python dependency to >= 2.4. Optionally, a one line
EE> patch (attached), will allow s3cmd to work properly with older python
EE> versions.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
