-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
The newly-autogenned twine is now using new upstream dependencies and so we need to update our YAML:
$ twine Traceback (most recent call last): File "/usr/lib/python-exec/python3.7/twine", line 33, in <module> sys.exit(load_entry_point('twine==4.0.0', 'console_scripts', 'twine')()) File "/usr/lib/python-exec/python3.7/twine", line 25, in importlib_load_entry_point return next(matches).load() File "/usr/lib/python3.7/site-packages/importlib_metadata/__init__.py", line 203, in load module = import_module(match.group('module')) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/lib/python3.7/site-packages/twine/__main__.py", line 22, in <module> from twine import cli File "/usr/lib/python3.7/site-packages/twine/cli.py", line 19, in <module> import rich ModuleNotFoundError: No module named 'rich'
- relates to
-
FL-9074 dev-python/typing-extensions-4.0.0 completely changed their build system, breaking autogen
- Closed