Andreas Vester
Andreas Vester
I am facing the same issue here. Another workaround could be to manually download the package(s) that causes the error from your private repo to your local machine. For example,...
I am also wondering why we need to put the private repo into ``pyproject.toml`` at all? We have to configure it in the actual ``poetry`` configuration, too (https://python-poetry.org/docs/repositories/#adding-a-repository)? Why can't...
Any kind of response would be appreciated.
If I can't get rid of the ``[[tool.poetry.source]]`` section in ``pyproject.toml``, I am not able to commit my code to GitHub at all for the simple reason that corporate rules...
@finswimmer To be honest, I haven't thought about a supply chain attack because the packages on our corporate private repo are exactly the same as on pypi. In fact, we...
@neersighted I am not saying that there is an easy solution to this problem. All I can say is that putting a private repo into pyproject.toml doesn't make any sense...
> @PidgeyBE So probably you can set the env var `PIP_INDEX_URL` to guide pip/poetry to the right index? I did try the following without success: `set PIP_INDEX_URL=https://:@foo.bar/simple/` When trying to...
@JulianSobott This solution worked for me. Thanks!
I can give it a try. I am not familiar with JS (more a Python guy), however, as far as I can tell, I need to insert a new variable...
What I don't like about this solution is the fact I don't want to reveal any internal server names in my ``pyproject.toml`` file. If I do that, committing to VCS...