We would check in the resulting image, so any Java dependency would only be
for when we update the image.
On Wed, Jan 3, 2018, 01:33 Paul Rudin, wrote:
> Brett Cannon writes:
>
> > On Tue, 2 Jan 2018 at 05:25 Yahya Abou 'Imran >
On Wed, Jan 3, 2018 at 8:24 AM, Random832 wrote:
> On Sun, Dec 31, 2017, at 00:33, Guido van Rossum wrote:
> > I'm not keen on this recommendation. An argument that takes a Set[Foo]
> > would mean that in order to specify:
> > - no flags: you'd have to pass set() -- you
On Sun, Dec 31, 2017, at 00:33, Guido van Rossum wrote:
> I'm not keen on this recommendation. An argument that takes a Set[Foo]
> would mean that in order to specify:
> - no flags: you'd have to pass set() -- you can't use {} since that's an
> empty dict, not an empty set
Optional[Set[Foo]]?
>
Brett Cannon writes:
> On Tue, 2 Jan 2018 at 05:25 Yahya Abou 'Imran b1ysje57in+bqq9rb...@public.gmane.org> wrote:
>
> At the end of the day, I found that plantuml is the most suitable tool for
> this.
>
> Right, but when I look at
You can embed plantuml directives in rst, and possibly the code, and use
sphinxcontrib-plantuml which at least keeps the diagrams for
documentation close to the code.
pyplantuml claims to be able to extract the infromation directly from
the code, (https://github.com/cb109/pyplantuml), but