{"action":"closed","issue":{"url":"https://api.github.com/repos/pypa/pipenv/issues/1811","repository_url":"https://api.github.com/repos/pypa/pipenv","labels_url":"https://api.github.com/repos/pypa/pipenv/issues/1811/labels{/name}","comments_url":"https://api.github.com/repos/pypa/pipenv/issues/1811/comments","events_url":"https://api.github.com/repos/pypa/pipenv/issues/1811/events","html_url":"https://github.com/pypa/pipenv/issues/1811","id":307094533,"number":1811,"title":"Using pipenv with a mono-repo and subdirectory dependencies and git causes weirdness","user":{"login":"LegoStormtroopr","id":2173174,"avatar_url":"https://avatars2.githubusercontent.com/u/2173174?v=4","gravatar_id":"","url":"https://api.github.com/users/LegoStormtroopr","html_url":"https://github.com/LegoStormtroopr","followers_url":"https://api.github.com/users/LegoStormtroopr/followers","following_url":"https://api.github.com/users/LegoStormtroopr/following{/other_user}","gists_url":"https://api.github.com/users/LegoStormtroopr/gists{/gist_id}","starred_url":"https://api.github.com/users/LegoStormtroopr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LegoStormtroopr/subscriptions","organizations_url":"https://api.github.com/users/LegoStormtroopr/orgs","repos_url":"https://api.github.com/users/LegoStormtroopr/repos","events_url":"https://api.github.com/users/LegoStormtroopr/events{/privacy}","received_events_url":"https://api.github.com/users/LegoStormtroopr/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-21T01:30:05Z","updated_at":"2018-03-21T03:41:28Z","closed_at":"2018-03-21T03:41:28Z","author_association":"NONE","body":"I am working on a project that uses a mono-repo and want my Pipfile to have subdirectories in that project as dependencies.\r\n\r\nIf I lock the following `Pipfile`:\r\n```\r\n[[source]]\r\nurl = \"https://pypi.python.org/simple\"\r\nverify_ssl = true\r\nname = \"pypi\"\r\n\r\n[dev-packages]\r\n\r\n[packages]\r\ndjango = \"~=1.11\"\r\n\"aristotle-cloud\" = {path = \"./python/aristotle-cloud\", editable = false}\r\n\r\n[requires]\r\npython_version = \"3.6\"\r\n```\r\n\r\nI get the following entry in my `Pipfile.lock`\r\n\r\n```\r\n    \"default\": {\r\n        \"aristotle-cloud\": {\r\n            \"editable\": false,\r\n            \"path\": \"./python/aristotle-cloud\"\r\n        },\r\n\r\n```\r\n\r\nBut as soon as any git dependency shows up, for example:\r\n```\r\n[packages]\r\ndjango = \"~=1.11\"\r\ndjango-data-importer = {ref = \"master\", git = \"https://github.com/LegoStormtroopr/django-data-importer\"}\r\n\"aristotle-cloud\" = {path = \"./python/aristotle-cloud\", editable = false}\r\n```\r\n\r\nLocking it now produces this entry in the `Pipfile.lock` file:\r\n\r\n```\r\n        \"aristotle-cloud\": {\r\n            \"editable\": true,\r\n            \"git\": \"https://github.com/LegoStormtroopr/aristotle-cloud\",\r\n            \"ref\": \"ccc9b36237fdde97d68cf4b101ca926dbce2aef8\",\r\n            \"subdirectory\": \"python/aristotle-cloud\"\r\n        },\r\n\r\n```\r\n\r\nI'm guessing that its picking up the fact that the file is in a git repo, but this isn't what I want. What I want is to lock the Pipfile to still require the subdirectorys when it is checked out, and install all of the packages in it from that directory, not have it go and try and fetch a different commit and install from there (which in this case it can't because its a private repo).\r\n"}}
{"actor":{"display_login":"techalchemy"}}