Does the graph take into account dependencies of the tests as well? A few
months ago I started on what I thought was a leaf, but its tests had
dependences on other modules that forced me to look at porting other
modules first.
On Thu, May 22, 2014 at 10:54 AM, Maxim Lacrima wrote:
> Hi Jean-Pau
Hi Jean-Paul,
Thanks for your advice.
Since nobody suggested a tool I created one myself, and here is a "graph"
for `twisted.web.client`: http://jsfiddle.net/gu8DX/embedded/result/ . It's
not a completely correct graph (because a node will miss edges to modules,
that have already been imported ea
On 10:50 am, ita...@itamarst.org wrote:
So what is a recommended workflow?
See https://twistedmatrix.com/trac/wiki/Plan/Python3
Something missing from that page is the very helpful tool that someone
(sorry, I forget who) developed at PyCon for rendering the module
dependency graph including
Thanks. That wiki page has enough info to get started.
On 20 May 2014 13:50, Itamar Turner-Trauring wrote:
> On 05/20/2014 05:40 AM, Maxim Lacrima wrote:
>
> Hello!
>
> I can see that Python 3 support in Twisted is incomplete. I was able to
> `pip install twisted` on Python 3, but I couldn't
On 05/20/2014 05:40 AM, Maxim Lacrima wrote:
Hello!
I can see that Python 3 support in Twisted is incomplete. I was able
to `pip install twisted` on Python 3, but I couldn't run a simple
example program using Twisted Agent.
A simple `from twisted.web.client import Agent` causes `ImportError:
Hello!
I can see that Python 3 support in Twisted is incomplete. I was able to
`pip install twisted` on Python 3, but I couldn't run a simple example
program using Twisted Agent.
A simple `from twisted.web.client import Agent` causes `ImportError: No
module named 'twisted.python.systemd'`
I woul
