Matt Davis

The new command for handling requirements is `pipenv requirements` and `pipenv lock -r` and `install -r` have been dropped. Please revisit this issue, I am willing to reopen it but...

@kaptajnen would a `--no-index` option to the `requirements` command that excluded any `-i ` lines be a suitable solution?

@EugeniuZ there is an enhancement that should be made to the `requirements` command for this case. Ideally someone that is setup to utilize this case could also work on the...

As a workaround, couldn't @RintaroMiyamoto specify the variables in the same way in the Pipfile? `"sources": [ "url":"https://${USER}:${ACCESS_TOKEN}@gitlab.com/private/repo" ]`

> What is the preferred way to generate a requirements.txt file with private repo (and credentials) after 2022.8.5? `pipenv lock -r` does variable substitution (as of 2022.8.5) while `pipenv requirements`...

@dennisvang Just wondering--Does it work if you define it with the variable not in the quotes? Like this: `my_editable_package = {path = ${HOME}"/my_editable_package", editable = true}`

@EugeniuZ or @EugeniuZ -- have you tried defining your sources like this: `"sources": [ "url":"https://${USER}:${ACCESS_TOKEN}@gitlab.com/private/repo" ]`

That is really odd -- how would downgrading setuptools change the python location?

@abouletupjv Can you re-check with `pipenv==2022.8.24`?

I wonder if your virtualenv was just created on a much older version? Can you try upgrading to pipenv, version 2022.8.30 and then re-create your virtualenv with `pipenv --rm` and...