{"action":"created","issue":{"url":"https://api.github.com/repos/pypa/pipenv/issues/2576","repository_url":"https://api.github.com/repos/pypa/pipenv","labels_url":"https://api.github.com/repos/pypa/pipenv/issues/2576/labels{/name}","comments_url":"https://api.github.com/repos/pypa/pipenv/issues/2576/comments","events_url":"https://api.github.com/repos/pypa/pipenv/issues/2576/events","html_url":"https://github.com/pypa/pipenv/issues/2576","id":340718635,"node_id":"MDU6SXNzdWUzNDA3MTg2MzU=","number":2576,"title":"Pipenv does not pull new ref from git when Pipfile is updated","user":{"login":"arielnmz","id":24735547,"node_id":"MDQ6VXNlcjI0NzM1NTQ3","avatar_url":"https://avatars0.githubusercontent.com/u/24735547?v=4","gravatar_id":"","url":"https://api.github.com/users/arielnmz","html_url":"https://github.com/arielnmz","followers_url":"https://api.github.com/users/arielnmz/followers","following_url":"https://api.github.com/users/arielnmz/following{/other_user}","gists_url":"https://api.github.com/users/arielnmz/gists{/gist_id}","starred_url":"https://api.github.com/users/arielnmz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arielnmz/subscriptions","organizations_url":"https://api.github.com/users/arielnmz/orgs","repos_url":"https://api.github.com/users/arielnmz/repos","events_url":"https://api.github.com/users/arielnmz/events{/privacy}","received_events_url":"https://api.github.com/users/arielnmz/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-07-12T16:52:23Z","updated_at":"2018-08-25T16:11:38Z","closed_at":"2018-07-12T20:29:08Z","author_association":"NONE","body":"##### Issue description\r\n\r\nI am using a small lib that I pull from git using its tag, this is how the entry looks in the Pipfile:\r\n\r\n`my_lib = {git = \"ssh://git@bitbucket.org/user/my_lib.git\", ref = \"v0.2.0\"}`\r\n\r\nI did some changes and pushed a new tag, so I updated my Pipfile accordingly\r\n\r\n`my_lib = {git = \"ssh://git@bitbucket.org/user/my_lib.git\", ref = \"v0.2.1\"}`\r\n\r\nI then locked dependencies:\r\n\r\n`pipenv lock`\r\n\r\nThis is how the lib entry looks in the Pipenv.lock:\r\n\r\n```\r\n\"nopal-framework-django\": {\r\n    \"git\": \"ssh://git@bitbucket.org/user/my_lib.git\",\r\n    \"ref\": \"v0.2.1\"\r\n},\r\n```\r\n\r\nAnd sync'ed packages:\r\n\r\n`$ pipenv sync`\r\n\r\n##### Expected result\r\n\r\nI expect the correct tag to be pulled\r\n\r\n##### Actual result\r\n\r\nAs the title suggests the package is not being installed correctly, as the graph shows otherwise:\r\n\r\n`$ pipenv graph`\r\n\r\n```\r\nmy-lib==0.2.0\r\n  - django [required: Any, installed: 2.0.7]\r\n    - pytz [required: Any, installed: 2018.5]\r\n  - djangorestframework [required: Any, installed: 3.8.2]\r\n```\r\n\r\n##### Steps to replicate\r\n\r\nI tried this on two different environments with the same Pipfile and package\r\n\r\n1. Create a new Pipfile\r\n2. Add a git entry\r\n3. Lock and sync\r\n4. Change the ref in the Pipfile\r\n5. Lock and sync again\r\n6. Graph still shows the old package\r\n\r\nOne way around this is to just remove the package and reinstall it with the desired ref\r\n\r\n-------------------------------------------------------------------------------\r\n\r\nPlease run `$ pipenv --support`, and paste the results here. Don't put backticks (`` ` ``) around it! The output already contains Markdown formatting.\r\n\r\n`Error: no such option: --support`\r\n"},"comment":{"url":"https://api.github.com/repos/pypa/pipenv/issues/comments/415979593","html_url":"https://github.com/pypa/pipenv/issues/2576#issuecomment-415979593","issue_url":"https://api.github.com/repos/pypa/pipenv/issues/2576","id":415979593,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNTk3OTU5Mw==","user":{"login":"techalchemy","id":954310,"node_id":"MDQ6VXNlcjk1NDMxMA==","avatar_url":"https://avatars0.githubusercontent.com/u/954310?v=4","gravatar_id":"","url":"https://api.github.com/users/techalchemy","html_url":"https://github.com/techalchemy","followers_url":"https://api.github.com/users/techalchemy/followers","following_url":"https://api.github.com/users/techalchemy/following{/other_user}","gists_url":"https://api.github.com/users/techalchemy/gists{/gist_id}","starred_url":"https://api.github.com/users/techalchemy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/techalchemy/subscriptions","organizations_url":"https://api.github.com/users/techalchemy/orgs","repos_url":"https://api.github.com/users/techalchemy/repos","events_url":"https://api.github.com/users/techalchemy/events{/privacy}","received_events_url":"https://api.github.com/users/techalchemy/received_events","type":"User","site_admin":false},"created_at":"2018-08-25T16:11:38Z","updated_at":"2018-08-25T16:11:38Z","author_association":"MEMBER","body":"non-editable installations don't resolve dependencies at all; it simply takes whatever you  say is the url and installs it using pip.  By default pip won't upgrade a package it has installed already (by name) unless you tell it to upgrade"}}
{"actor":{"display_login":"techalchemy"}}