``twisted.python.code`` package proposal about twisted HOT 8 OPEN

Hello @ghickman, I did not know the ccbv tool, great job documenting django!

It would be awesome to combine our efforts to maintain a framework that works for everyone. I'm currently still in the development process of a first version of the passmanager. You can review it here: https://github.com/tristanlatr/libstatic/tree/passmanager/libstatic/_lib/passmanager.

I've read in the linked ticket that you're looking for something that preserves the code formatting, ast does not preserves such things. But if this requirement is only to show the source code of methods, it can be easily overcome by generating the code html from tokens instead of ast, and these can easily be matched to ast nodes with asttokens.

Anyway, If I believe the ccbv readme, your requirements fits into what this framework is able to provide. So let's try to collaborate :)

from twisted.

Thanks for the proposal.

just a quick comment

Why not move this into a separate repo twisted/code ?

My understanding is that the focus of twisted/twisted is about async i/o or async network communications.

My understanding is that the focus of the current proposal is code analysis.

from twisted.

I’m not against a putting it into a new repository. The only constraint for it to work with pydoctor is that it should be published as a debian package.

from twisted.

I also wouldn't have thought of Twisted first when thinking about where such functionality should live.

If the intended user is pydoctor and you want to avoid the overhead associated with distributing a brand new package, maybe pydoctor is the right place for it.

from twisted.

If the code is useful, most probably distribution developers will create a package for it.
Since it's a standard Python package, I expect that all distributions have a template for it.

Is this someting that you think will be used by people in production ? or as part of the operating system / GNOME/ KDE ?

Even in production, in the last 15 years I have always deployed things using virtualenv and private PyPI mirrors.

from twisted.

You have very good points Adi. The thing is pydoctor is more an application than a library. But I guess I could find some room for it in a sub package; or in a new repo.

Also I wanted to open the discussion here to see if there was any interest into helping review the code and maintain this library with me.

I’ve read that twisted is hiring dev(s) to review code, would this kind of project would fall into the scope ?

from twisted.

You have very good points Adi. The thing is pydoctor is more an application than a library. But I guess I could find some room for it in a sub package; or in a new repo.

Also I wanted to open the discussion here to see if there was any interest into helping review the code and maintain this library with me.

I’ve read that twisted is hiring dev(s) to review code, would this kind of project would fall into the scope ?

As part of the Twisted org, it would, but "hiring dev(s)" is a pretty ambitious way to describe paying for a few hours of time :).

However, if we can raise some more money, we can increase the amount of time available for this sort of work.

from twisted.

Having this in a separate repo would make it easier for other tools to pull it in. I'm interested in this because we, the maintainers of ccbv, have long been thinking about moving away from inspect to something that doesn't trigger import side effects. Having a library, like pathmanager, readily available to us would be great!

from twisted.