#3351: trac 0.9.5 not worked with python 2.5b1
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner: mgood
Type: defect | Status: assigned
Priority: lowest | Milestone: 0.9.7
Component: general | Version: 0.9.5
Severity: minor | Resolution:
Keywords: |
-----------------------+----------------------------------------------------
Changes (by mgood):
* owner: cboos => mgood
* status: new => assigned
Comment:
Replying to [comment:5 [EMAIL PROTECTED]:
> Anyway, the problem is not releate to {{{__future__}}} but as you can
see to the patch that I have attached to #3377 the error is generated by
the line 15 of file trac/scripts/admin.py that is:
''(summarizing our discussion on IRC):'' This ''is'' specific to importing
from `__future__` since it's a special module used to change the behavior
of the Python parser. So, since it will affect the parsing of the rest of
the module, the `__future__` imports need to occur before other code.
This fix is so trivial I'll go ahead and commit it, but I think cboos and
cmlenz are right that if there's much work needed to make Trac 0.9.x
compatible with Python 2.5 it's not really worth it since [milestone:0.10]
should be done before the Python release is finalized.
--
Ticket URL: <http://trac.edgewall.org/ticket/3351>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
