You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is created correctly. develop = true is the same as -e (--editable) for pip. #258 is a bugfix for #145.
When installing via pip, it does not copy the package files into the target directory. It puts the dist-info folder, and a package_name.pth file.
That's what develop/editable should do.
Having said that, a PR introducing a flag for the export command to ignore the value of develop and export all dependencies as non-editable would probably be accepted.
@radoering, I realize you folks are busy but it is worth noting that this change broke dependency resolution for folks using poetry with a monorepo, because pip can't resolve multiple versions of editable dependencies. We're currently stuck on an old version of poetry-plugin-export because of this.
@williamhakim10 Do you pass --no-deps to pip? This often resolves such issues. By the way, it does not make sense to let pip resolve dependencies again, i.e. not using --no-deps, because the exported requirements.txt contains all resolved direct and transitive dependencies.
When exporting with a relative package, with
develop = true
, therequirements.txt
file is not created correctly.pyproject.toml
requirements.txt
with1.7.1
requirements.txt
with1.8.0
When installing via pip, it does not copy the package files into the target directory. It puts the dist-info folder, and a
package_name.pth
file.The text was updated successfully, but these errors were encountered: