Jacob Roberts

I think we hit a similar issue because we used a DNS hostname and not an IP address.... Speculative, but maybe helpful for anyone who comes here henceforth

@RobertCraigie I think we could push this further get rid of the `requirements/coverage.txt` and `requirements/dev.txt` and really keep everything in one place for "developers"

@RobertCraigie is this something that I should continue on? The base problem is that as a dev getting the IDE to work across all the different environments we have is...

If you wanted to separate them further I think we would want to switch to [poetry dependency groups](https://python-poetry.org/docs/master/managing-dependencies/#dependency-groups) -- which I think would get around the issue you saw in...

@njzjz one thing I am slightly confused about... We do publish a `manylinux_2_12_x86_64` version so according to the PEP if you use GLIBC `2_28` that should in theory abide by...

I am getting an error "Cannot find module 'meteor/templating'", etc. when I try to mirror your above. Any suggestions? ``` import { Template } from 'meteor/templating' import { Blaze }...

For anyone coming at this from Typescript, relevant conversation [here](https://github.com/barbatus/typescript/issues/6)

So now that I am getting my project to compile, I have the same issue as @sys13 , which I think has to do with the intersection of routing between...

+1 for @ianmartorell to choose what published user property gets displayed. Would be great to let the author decide between full name, username, email, etc.

Relevant code is here: https://github.com/sytsereitsma/mdbook-plantuml/blob/d1dd726c13671b80eae089cfb2f35c12548672d5/src/plantuml_backend_factory.rs#L15