I recently upgraded TracXmlRpcPlugin to version 1.0.6 (or HEAD ) and
some data surces I had implemented in TracGViz [2]_ plugin fail. The
reason is that the later performs (almost) direct calls to the public
methods defined by RPC handlers, and OTOH it seems that since rev
[email protected] [1]_ the plugin «changes to datetime handling, by
converting any timestamps to Python datetime before arguments are
passed to methods». Therefore the former assumption of RPC handler
accepting instances of DateTime as parameters is not valid anymore.
IMO TracGViz should work with both versions (1.0.0 and >=1.0.6) of
XmlRpcPlugin, but if I patch it to make it work with 1.0.6, for
instance, then it stops working with 1.0.0. So I need to find a way to
determine at run-time which type is the one being accepted by RPC
handlers in order supply the right object as a parameter.
Q:
- How can I do that ? I mean, what's the ( right | most
straightforward | most reliable )
way to determine whether instances of `DateTime` or OTOH instances
of `datetime`
are accepted by RPC handlers ?
Thanks in advance !
.. [1] Changeset 6046
(http://trac-hacks.org/changeset/6046)
.. [2] TracGViz plugin
(https://opensvn.csie.org/traccgi/swlcu/wiki/En/Devel/TracGViz)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
