Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Also distribute CDK Toolkit via pip

See original GitHub issue

Only relevant once the Python bindings are out, but a comment has been made that it will be jarring to Python developers to have to npm install the Toolkit, and they would prefer to pip install it.

Issue Analytics

State:
Created 5 years ago
Reactions:4
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

jeshancommented, Sep 6, 2019

I think considering by language-specific is suboptimal as it won’t scale. If npm isn’t desirable by Python programmers, then the same argument could be made by the community behind each of the CDK-supported languages, e.g a .NET programmer could say that neither pip nor npm is desirable.

Maybe a better solution is to provide a native CDK binary per OS with pkg or nexe

1reaction

bgdnlpcommented, Sep 2, 2019

Regarding installing a venv, you don’t have to initialize a language/environment using --init. It’s just there as a helper. You can start blank, nothing the CDK sets up there is actually required.

Personally, I only used --init the first time I tried the CDK, after that I found that it just gets in the way.

Maybe the documentation and examples should make that clearer.