Poetry doesn't resolve on MacOs Mojave #1047

Activity

1. tuchandra commented on Apr 23, 2019

   

   tuchandra

   on Apr 23, 2019

   More actions

   Tried this out because I'm also running Mojave on my Mac, but I wasn't able to repro. I got the following output:

   Package operations: 24 installs, 0 updates, 0 removals
   
   Writing lock file
   
     - Installing pytz (2019.1)
     - Installing sqlparse (0.3.0)
     - Installing appdirs (1.4.3)
     - Installing atomicwrites (1.3.0)
     - Installing attrs (19.1.0)
     - Installing click (7.0)
     - Installing django (2.2)
     - Installing entrypoints (0.3)
     - Installing mccabe (0.6.1)
     - Installing more-itertools (7.0.0)
     - Installing pluggy (0.9.0)
     - Installing py (1.8.0)
     - Installing pycodestyle (2.5.0)
     - Installing pyflakes (2.1.1)
     - Installing six (1.12.0)
     - Installing toml (0.10.0)
     - Installing black (19.3b0)
     - Installing coverage (4.5.3)
     - Installing django-debug-toolbar (1.11)
     - Installing flake8 (3.7.7)
     - Installing mistune (0.8.4)
     - Installing psycopg2-binary (2.8.2)
     - Installing pytest (4.4.1)
     - Installing python-decouple (3.1)
   

   I am on Poetry 0.12.11, though; what happens if you downgrade? Perhaps a bug was introduced in the newest release.
2. wilfredinni commented on Apr 23, 2019

   

   wilfredinni

   on Apr 23, 2019

   Last edited by wilfredinni

   Author

   More actions

   @tuchandra the first time I install the dependencies I have no problems either. Can you try to use poetry update and see what happens now? Thank you.
3. tuchandra commented on Apr 24, 2019

   

   tuchandra

   on Apr 24, 2019

   More actions

   Running it again works fine:

   Updating dependencies
   Resolving dependencies... (0.3s)
   
   Nothing to install or update
   

   :/
4. wilfredinni commented on Apr 25, 2019

   

   wilfredinni

   on Apr 25, 2019

   Author

   More actions

   Removed Poetry, all the virtualenvs and cleaned the cache folder, then reinstalled it. All is good now.
5. floer32 commented on May 5, 2019

   

   floer32

   on May 5, 2019

   More actions

   @wilfredinni sounds about right

   Here is a related issue, which may offer a bit of explanation (TLDR has to do with cachecontrol/filelock libs)

   #832 (comment)
6. floer32 commented on May 5, 2019

   

   floer32

   on May 5, 2019

   More actions

   @wilfredinni Since this seemingly is not about OS, and since there are known resolutions, could you edit the ticket title and/or close the ticket?
7. wilfredinni commented on May 5, 2019

   

   wilfredinni

   on May 5, 2019

   Author

   More actions

   @wilfredinni Since this seemingly is not about OS, and since there are known resolutions, could you edit the ticket title and/or close the ticket?

   Sure.
8. wilfredinni

   closed this as completedon May 5, 2019
9. github-actions commented on Mar 3, 2024

   

   github-actionsBot

   on Mar 3, 2024 – with GitHub Actions

   More actions

   This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
10. github-actions

    locked as resolved and limited conversation to collaborators on Mar 3, 2024