Conflict with [email protected] about nitpick HOT 7 CLOSED

Hello @isac322, thanks for the bug report.

This bug uiri/toml#295 was fixed here: uiri/toml@9be6458, but a new toml version was not released yet.
Latest one is still 0.10.1.

To fix this, I will install uiri/toml@9be6458 directly, using Poetry.

This can lead to issues though, if you already have toml version 0.10.1 installed.
You will need to remove and reinstall it, otherwise Poetry doesn't detect the version change (at least this is what happened to me while testing locally).

from nitpick.

🎉 This issue has been resolved in version 0.23.0 🎉

The release is available on:

• v0.23.0
• GitHub release

Your semantic-release bot 📦🚀

from nitpick.

@andreoliwa - This issue isn't fixed. Seems like nitpick still depends on toml==0.10.0. I installed the latest version of toml==0.10.1 and then trying to install nitpick gave me the same error as above.

Using version ^0.23.0 for nitpick

Updating dependencies
Resolving dependencies... (0.4s)

  SolverProblemError

  Because no versions of nitpick match >0.23.0,<0.24.0
   and nitpick (0.23.0) depends on toml (<0.10.1), nitpick (>=0.23.0,<0.24.0) requires toml (<0.10.1).
  So, because raa-django depends on both toml (^0.10.1) and nitpick (^0.23.0), version solving failed.

  at ~/.pyenv/versions/3.8.3/envs/3.8.3-raa/lib/python3.8/site-packages/poetry/puzzle/solver.py:241 in _solve
      237│             packages = result.packages
      238│         except OverrideNeeded as e:
      239│             return self.solve_in_compatibility_mode(e.overrides, use_latest=use_latest)
      240│         except SolveFailure as e:
    → 241│             raise SolverProblemError(e)
      242│ 
      243│         results = dict(
      244│             depth_first_search(
      245│                 PackageNode(self._package, packages), aggregate_package_nodes

from nitpick.

@andreoliwa - This issue isn't fixed. Seems like nitpick still depends on toml==0.10.0. I installed the latest version of toml==0.10.1 and then trying to install nitpick gave me the same error as above.

@gghildyal. Yes, I thought I had it fixed, but it didn't work (I wrote something above: #200 (comment))

@andreoliwa FYI. toml 0.10.2 is released!

@isac322 Thanks for the heads-up. Cool, I will try to upgrade toml again now.

from nitpick.

🎉 This issue has been resolved in version 0.23.1 🎉

The release is available on:

• v0.23.1
• GitHub release

Your semantic-release bot 📦🚀

from nitpick.

Unfortunately I cannot fix this issue.
I need to wait until a new toml version 0.10.2 is released with uiri/toml@9be6458. 😞

After a few hours banging my head against the wall, I will have to revert this change.
Using a Git commit doesn't work for package dependencies.
I can't upload a new package to PyPI, it fails with the error:

HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
Invalid value for requires_dist. Error: Can't have direct dependency: 'toml @ git+https://github.com/uiri/toml.git@9be6458'

See:

• pypa/pip#6301 (comment)
• pypi/warehouse#7136 (comment)
• python - How can I use git repos as dependencies for my PyPi package? - Stack Overflow

As a workaround while we wait for a new toml release, you can run nitpick as a pre-commit hook instead.
This way, Nitpick will be installed in an isolated repo, and it won't affect black in your virtualenv.

You can also run black as a pre-commit hook.

These are the recommended ways to run these tools IMHO. 😉

from nitpick.

@andreoliwa FYI. toml 0.10.2 is released!

from nitpick.