failed to poetry add -D black using python 3.10-rc2, 3.9 works well

[laoshaw]

• [X ] I am on the latest Poetry version.

• [ x] I have searched the issues of this repo and believe that this is not a duplicate.

• [ x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: ubuntu 20.04

• Poetry version: 1.1.10

• Link of a Gist with the contents of your pyproject.toml file: the initial default one right after poetry new

Issue

Works for 3.8/3.9 but not 3.10-rc2:

poetry new X; cd X; poetry add -D -vvv black

Finding the necessary packages for the current system

Package operations: 15 installs, 0 updates, 0 removals, 3 skipped

  • Removing atomicwrites (1.4.0): Pending...
  • Removing atomicwrites (1.4.0): Skipped for the following reason: Not currently installed
  • Removing colorama (0.4.4): Pending...
  • Removing colorama (0.4.4): Skipped for the following reason: Not currently installed
  • Removing typing-extensions (3.10.0.2): Pending...
  • Removing typing-extensions (3.10.0.2): Skipped for the following reason: Not currently installed
  • Installing pyparsing (2.4.7): Pending...
  • Installing pyparsing (2.4.7): Failed

  JSONDecodeError

  Expecting value: line 1 column 1 (char 0)

  at /usr/lib/python3.10/json/decoder.py:355 in raw_decode
      351│         """
      352│         try:
      353│             obj, end = self.scan_once(s, idx)
      354│         except StopIteration as err:
    → 355│             raise JSONDecodeError("Expecting value", s, err.value) from None
      356│         return obj, end
      357│ 


Failed to add packages, reverting the pyproject.toml file to its original content.

[laoshaw]

This same errors(decoder.py:355 in raw_code) seems happening with many other packages(isort, marshmellow,etc)

[cpressland]

I'm running into the same thing on macOS Monterey /w pipx installed Poetry on 3.10.0.

EDIT: Running poetry install over and over eventually successfully installs all packages.

[mkniewallner]

It seems that this issue was fixed by #4592, so closing it.

[github-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.