[BUG] Should fail hard when installing packages that want 2to3 #2769

plumdog · 2021-09-06T16:29:08Z

setuptools version

setuptools==58.0.0

Python version

Python 3.9

OS

Linux

Additional environment information

No response

Description

Tried to install a package that uses 2to3 (specifically https://pypi.org/project/demjson/), got a message from pip like:

Successfully installed demjson-2.2.3

But really it wasn't successful, and then get confusing SyntaxError exceptions.

Expected behavior

I have now worked out that this is because of the change to remove 2to3 from setuptools, which I think is a perfectly reasonable change, and because my setuptools version wasn't pinned. But setuptools is not doing something the package is asking for, and the result is going to be something that does not run (though I guess there are caveats here).

I would have expected to get an error like "This module wants to use 2to3, but this is not supported [link to github issue about removing 2to3 support]". At least, that would certainly have saved me time.

How to Reproduce

Install demjson==2.2.3 with setuptools==58.0.0. Attempt to import and get a syntax error.

Output

$ pip install -U setuptools==58.0.0 && pip install demjson==2.2.3 && python -c 'import demjson'
Collecting setuptools==58.0.0
  Using cached setuptools-58.0.0-py3-none-any.whl (816 kB)
Installing collected packages: setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 56.0.0
    Uninstalling setuptools-56.0.0:
      Successfully uninstalled setuptools-56.0.0
Successfully installed setuptools-58.0.0
Collecting demjson==2.2.3
  Using cached demjson-2.2.3.tar.gz (131 kB)
Using legacy 'setup.py install' for demjson, since package 'wheel' is not installed.
Installing collected packages: demjson
    Running setup.py install for demjson ... done
Successfully installed demjson-2.2.3
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/user/example/venv/lib/python3.9/site-packages/demjson.py", line 645
    class json_int( (1L).__class__ ):    # Have to specify base this way to satisfy 2to3
                      ^
SyntaxError: invalid syntax

Code of Conduct

I agree to follow the PSF Code of Conduct

The text was updated successfully, but these errors were encountered:

jaraco · 2021-09-06T16:52:23Z

Good suggestion. I think I agree.

arpheno · 2021-09-07T16:51:03Z

I think this broke a lot of builds unintentionally.

ikapelyukhin · 2021-09-07T17:01:08Z

I think this broke a lot of builds unintentionally.

It sure did. 😬

plumdog · 2021-09-07T17:52:43Z

My intention when raising this issue was to make it so builds fail, rather than getting runtime errors because 2to3 wasn't applied to a dependency that needs it. That is, this behaviour breaks builds intentionally where the setuptools version and the dependencies are incompatible.

mattclay · 2021-09-07T18:09:11Z

@plumdog Unfortunately the implementation in #2770 also breaks builds which explicitly disable the use_2to3 feature, which would otherwise install correctly.

plumdog · 2021-09-07T18:31:11Z

@mattclay Oh. 😬

…he no longer maintained uses use_2to3 which was deprecated in the most recent release of setuptools; see pypa/setuptools#2769)

The resolution of setuptools 2769 made any package using `use_2to3` to fail its build. This patch removes the flag, in support of outroducing rdflib-jsonld. References: * pypa/setuptools#2769 * RDFLib/rdflib#1405 Reported-by: Ralf Grubenmann <[email protected]> Signed-off-by: Alex Nelson <[email protected]>

The resolution of setuptools 2769 made any package using `use_2to3` to fail its build. This patch removes the flag, in support of outroducing rdflib-jsonld. The test suite is showing other follow-on patches will be necessary to fix matters 2to3 had been quietly fixing along the way. References: * pypa/setuptools#2769 * RDFLib/rdflib#1405 Reported-by: Ralf Grubenmann <[email protected]>

= 4.10.0 (20210907) * This is the first release of Beautiful Soup to only support Python 3. I dropped Python 2 support to maintain support for newer versions (58 and up) of setuptools. See: pypa/setuptools#2769 [bug=1942919] * The behavior of methods like .get_text() and .strings now differs depending on the type of tag. The change is visible with HTML tags like <script>, <style>, and <template>. Starting in 4.9.0, methods like get_text() returned no results on such tags, because the contents of those tags are not considered 'text' within the document as a whole. But a user who calls script.get_text() is working from a different definition of 'text' than a user who calls div.get_text()--otherwise there would be no need to call script.get_text() at all. In 4.10.0, the contents of (e.g.) a <script> tag are considered 'text' during a get_text() call on the tag itself, but not considered 'text' during a get_text() call on the tag's parent. Because of this change, calling get_text() on each child of a tag may now return a different result than calling get_text() on the tag itself. That's because different tags now have different understandings of what counts as 'text'. [bug=1906226] [bug=1868861] * NavigableString and its subclasses now implement the get_text() method, as well as the properties .strings and .stripped_strings. These methods will either return the string itself, or nothing, so the only reason to use this is when iterating over a list of mixed Tag and NavigableString objects. [bug=1904309] * The 'html5' formatter now treats attributes whose values are the empty string as HTML boolean attributes. Previously (and in other formatters), an attribute value must be set as None to be treated as a boolean attribute. In a future release, I plan to also give this behavior to the 'html' formatter. Patch by Isaac Muse. [bug=1915424] * The 'replace_with()' method now takes a variable number of arguments, and can be used to replace a single element with a sequence of elements. Patch by Bill Chandos. [rev=605] * Corrected output when the namespace prefix associated with a namespaced attribute is the empty string, as opposed to None. [bug=1915583] * Performance improvement when processing tags that speeds up overall tree construction by 2%. Patch by Morotti. [bug=1899358] * Corrected the use of special string container classes in cases when a single tag may contain strings with different containers; such as the <template> tag, which may contain both TemplateString objects and Comment objects. [bug=1913406] * The html.parser tree builder can now handle named entities found in the HTML5 spec in much the same way that the html5lib tree builder does. Note that the lxml HTML tree builder doesn't handle named entities this way. [bug=1924908] * Added a second way to pass specify encodings to UnicodeDammit and EncodingDetector, based on the order of precedence defined in the HTML5 spec, starting at: https://html.spec.whatwg.org/multipage/parsing.html#parsing-with-a-known-character-encoding Encodings in 'known_definite_encodings' are tried first, then byte-order-mark sniffing is run, then encodings in 'user_encodings' are tried. The old argument, 'override_encodings', is now a deprecated alias for 'known_definite_encodings'. This changes the default behavior of the html.parser and lxml tree builders, in a way that may slightly improve encoding detection but will probably have no effect. [bug=1889014] * Improve the warning issued when a directory name (as opposed to the name of a regular file) is passed as markup into the BeautifulSoup constructor. [bug=1913628] Signed-off-by: Zang Ruochen <[email protected]> Signed-off-by: Khem Raj <[email protected]>

= 4.10.0 (20210907) * This is the first release of Beautiful Soup to only support Python 3. I dropped Python 2 support to maintain support for newer versions (58 and up) of setuptools. See: pypa/setuptools#2769 [bug=1942919] * The behavior of methods like .get_text() and .strings now differs depending on the type of tag. The change is visible with HTML tags like <script>, <style>, and <template>. Starting in 4.9.0, methods like get_text() returned no results on such tags, because the contents of those tags are not considered 'text' within the document as a whole. But a user who calls script.get_text() is working from a different definition of 'text' than a user who calls div.get_text()--otherwise there would be no need to call script.get_text() at all. In 4.10.0, the contents of (e.g.) a <script> tag are considered 'text' during a get_text() call on the tag itself, but not considered 'text' during a get_text() call on the tag's parent. Because of this change, calling get_text() on each child of a tag may now return a different result than calling get_text() on the tag itself. That's because different tags now have different understandings of what counts as 'text'. [bug=1906226] [bug=1868861] * NavigableString and its subclasses now implement the get_text() method, as well as the properties .strings and .stripped_strings. These methods will either return the string itself, or nothing, so the only reason to use this is when iterating over a list of mixed Tag and NavigableString objects. [bug=1904309] * The 'html5' formatter now treats attributes whose values are the empty string as HTML boolean attributes. Previously (and in other formatters), an attribute value must be set as None to be treated as a boolean attribute. In a future release, I plan to also give this behavior to the 'html' formatter. Patch by Isaac Muse. [bug=1915424] * The 'replace_with()' method now takes a variable number of arguments, and can be used to replace a single element with a sequence of elements. Patch by Bill Chandos. [rev=605] * Corrected output when the namespace prefix associated with a namespaced attribute is the empty string, as opposed to None. [bug=1915583] * Performance improvement when processing tags that speeds up overall tree construction by 2%. Patch by Morotti. [bug=1899358] * Corrected the use of special string container classes in cases when a single tag may contain strings with different containers; such as the <template> tag, which may contain both TemplateString objects and Comment objects. [bug=1913406] * The html.parser tree builder can now handle named entities found in the HTML5 spec in much the same way that the html5lib tree builder does. Note that the lxml HTML tree builder doesn't handle named entities this way. [bug=1924908] * Added a second way to pass specify encodings to UnicodeDammit and EncodingDetector, based on the order of precedence defined in the HTML5 spec, starting at: https://html.spec.whatwg.org/multipage/parsing.html#parsing-with-a-known-character-encoding Encodings in 'known_definite_encodings' are tried first, then byte-order-mark sniffing is run, then encodings in 'user_encodings' are tried. The old argument, 'override_encodings', is now a deprecated alias for 'known_definite_encodings'. This changes the default behavior of the html.parser and lxml tree builders, in a way that may slightly improve encoding detection but will probably have no effect. [bug=1889014] * Improve the warning issued when a directory name (as opposed to the name of a regular file) is passed as markup into the BeautifulSoup constructor. [bug=1913628] Signed-off-by: Zang Ruochen <[email protected]> Signed-off-by: Khem Raj <[email protected]> Signed-off-by: Trevor Gamblin <[email protected]>

setuptools 58.0.0 and above fails to install due to issue pypa/setuptools#2769

Due to bug pypa/setuptools#2769

With the recent change in pypa/setuptools#2769, some wheels started to fail build immediately with an unpinned setuptools in isolation mode. Signed-off-by: Thulio Ferraz Assis <[email protected]>

ajnelson-nist · 2021-10-01T18:14:52Z

@jaraco , I apologize, I just found I'd forgotten to reply.

Your reasoning makes sense, and I won't push the issue further. What I hadn't appreciated fully is that 2to3-related breakage was supposed to be introduced with this major release. Thank you for the kind discussion.

With the recent change in pypa/setuptools#2769, some wheels started to fail build immediately with an unpinned setuptools in isolation mode. Signed-off-by: Thulio Ferraz Assis <[email protected]>

Gazelle plugin * Add new example to --deleted_packages * Update examples/build_file_generation/BUILD Co-authored-by: Jonathon Belotti <[email protected]> * fix: gazelle:exclude on coarse-grained Signed-off-by: Thulio Ferraz Assis <[email protected]> * fix: comment on Kinds() Co-authored-by: Jonathon Belotti <[email protected]> * owner: f0rmiga Signed-off-by: Thulio Ferraz Assis <[email protected]> * fix: build and setuptools pinned versions With the recent change in pypa/setuptools#2769, some wheels started to fail build immediately with an unpinned setuptools in isolation mode. Signed-off-by: Thulio Ferraz Assis <[email protected]> * refactor: use local_repository in examples Signed-off-by: Thulio Ferraz Assis <[email protected]> * bump: examples Bazel version Signed-off-by: Thulio Ferraz Assis <[email protected]> * fix: add missing .gitignore to example Signed-off-by: Thulio Ferraz Assis <[email protected]> * refactor: remove python_coarse_grained_generation Also add the python_generation_mode directive. Signed-off-by: Thulio Ferraz Assis <[email protected]> * fix: gazelle spam from org_golang_x_tools Signed-off-by: Thulio Ferraz Assis <[email protected]> * revert: example .bazelversion Signed-off-by: Thulio Ferraz Assis <[email protected]> * fix: simplify std_modules.py Signed-off-by: Thulio Ferraz Assis <[email protected]> * feat: test py_library without __init__.py Signed-off-by: Thulio Ferraz Assis <[email protected]> * feat: manifest generation tag manual Signed-off-by: Thulio Ferraz Assis <[email protected]> * fix: check std modules last Performing the check last is more correct and yields better performance, noticeable on large repositories. Signed-off-by: Thulio Ferraz Assis <[email protected]> Co-authored-by: Alex Eagle <[email protected]> Co-authored-by: Jonathon Belotti <[email protected]>

… to pypa/setuptools#2769

New setuptools versions stop deliberately building packages that use 2to3. See pypa/setuptools#2769 This option should have been removed in commit 3aeb6ff

setuptools 58.0.0 and above fails to install due to issue pypa/setuptools#2769

Due to bug pypa/setuptools#2769

4.11.1 (20220408) This release was done to ensure that the unit tests are packaged along with the released source. There are no functionality changes in this release, but there are a few other packaging changes: * The Japanese and Korean translations of the documentation are included. * The changelog is now packaged as CHANGELOG, and the license file is packaged as LICENSE. NEWS.txt and COPYING.txt are still present, but may be removed in the future. * TODO.txt is no longer packaged, since a TODO is not relevant for released code. 4.11.0 (20220407) * Ported unit tests to use pytest. * Added special string classes, RubyParenthesisString and RubyTextString, to make it possible to treat ruby text specially in get_text() calls. * It's now possible to customize the way output is indented by providing a value for the 'indent' argument to the Formatter constructor. The 'indent' argument works very similarly to the argument of the same name in the Python standard library's json.dump() function. * If the charset-normalizer Python module (https://pypi.org/project/charset-normalizer/) is installed, Beautiful Soup will use it to detect the character sets of incoming documents. This is also the module used by newer versions of the Requests library. For the sake of backwards compatibility, chardet and cchardet both take precedence if installed. * Added a workaround for an lxml bug (https://bugs.launchpad.net/lxml/+bug/1948551) that causes problems when parsing a Unicode string beginning with BYTE ORDER MARK. * Issue a warning when an HTML parser is used to parse a document that looks like XML but not XHTML. * Do a better job of keeping track of namespaces as an XML document is parsed, so that CSS selectors that use namespaces will do the right thing more often. * Some time ago, the misleadingly named "text" argument to find-type methods was renamed to the more accurate "string." But this supposed "renaming" didn't make it into important places like the method signatures or the docstrings. That's corrected in this version. "text" still works, but will give a DeprecationWarning. * Fixed a crash when pickling a BeautifulSoup object that has no tree builder. * Fixed a crash when overriding multi_valued_attributes and using the html5lib parser. * Standardized the wording of the MarkupResemblesLocatorWarning warnings to omit untrusted input and make the warnings less judgmental about what you ought to be doing. * Removed support for the iconv_codec library, which doesn't seem to exist anymore and was never put up on PyPI. (The closest replacement on PyPI, iconv_codecs, is GPL-licensed, so we can't use it--it's also quite old.) 4.10.0 (20210907) * This is the first release of Beautiful Soup to only support Python 3. I dropped Python 2 support to maintain support for newer versions (58 and up) of setuptools. See: pypa/setuptools#2769 * The behavior of methods like .get_text() and .strings now differs depending on the type of tag. The change is visible with HTML tags like <script>, <style>, and <template>. Starting in 4.9.0, methods like get_text() returned no results on such tags, because the contents of those tags are not considered 'text' within the document as a whole. But a user who calls script.get_text() is working from a different definition of 'text' than a user who calls div.get_text()--otherwise there would be no need to call script.get_text() at all. In 4.10.0, the contents of (e.g.) a <script> tag are considered 'text' during a get_text() call on the tag itself, but not considered 'text' during a get_text() call on the tag's parent. Because of this change, calling get_text() on each child of a tag may now return a different result than calling get_text() on the tag itself. That's because different tags now have different understandings of what counts as 'text'. * NavigableString and its subclasses now implement the get_text() method, as well as the properties .strings and .stripped_strings. These methods will either return the string itself, or nothing, so the only reason to use this is when iterating over a list of mixed Tag and NavigableString objects. * The 'html5' formatter now treats attributes whose values are the empty string as HTML boolean attributes. Previously (and in other formatters), an attribute value must be set as None to be treated as a boolean attribute. In a future release, I plan to also give this behavior to the 'html' formatter. Patch by Isaac Muse. * The 'replace_with()' method now takes a variable number of arguments, and can be used to replace a single element with a sequence of elements. Patch by Bill Chandos. [rev=605] * Corrected output when the namespace prefix associated with a namespaced attribute is the empty string, as opposed to None. * Performance improvement when processing tags that speeds up overall tree construction by 2%. Patch by Morotti. * Corrected the use of special string container classes in cases when a single tag may contain strings with different containers; such as the <template> tag, which may contain both TemplateString objects and Comment objects. * The html.parser tree builder can now handle named entities found in the HTML5 spec in much the same way that the html5lib tree builder does. Note that the lxml HTML tree builder doesn't handle named entities this way. * Added a second way to pass specify encodings to UnicodeDammit and EncodingDetector, based on the order of precedence defined in the HTML5 spec, starting at: https://html.spec.whatwg.org/multipage/parsing.html#parsing-with-a-known-character-encoding Encodings in 'known_definite_encodings' are tried first, then byte-order-mark sniffing is run, then encodings in 'user_encodings' are tried. The old argument, 'override_encodings', is now a deprecated alias for 'known_definite_encodings'. This changes the default behavior of the html.parser and lxml tree builders, in a way that may slightly improve encoding detection but will probably have no effect. * Improve the warning issued when a directory name (as opposed to the name of a regular file) is passed as markup into the BeautifulSoup constructor.

The resolution of setuptools 2769 made any package using `use_2to3` to fail its build. This patch removes the flag, in support of outroducing rdflib-jsonld. The test suite is showing other follow-on patches will be necessary to fix matters 2to3 had been quietly fixing along the way. However, this first patch does restore a working call to `pip install .` with up-to-date setuptools. Unit test results: This causes only the same five tests as were previously failing to fail. setuptools versions tested: * 41.2.0 * 58.0.4 References: * pypa/setuptools#2769 * RDFLib/rdflib#1405 Reported-by: Ralf Grubenmann <[email protected]> Signed-off-by: Alex Nelson <[email protected]>

= 4.10.0 (20210907) * This is the first release of Beautiful Soup to only support Python 3. I dropped Python 2 support to maintain support for newer versions (58 and up) of setuptools. See: pypa/setuptools#2769 [bug=1942919] * The behavior of methods like .get_text() and .strings now differs depending on the type of tag. The change is visible with HTML tags like <script>, <style>, and <template>. Starting in 4.9.0, methods like get_text() returned no results on such tags, because the contents of those tags are not considered 'text' within the document as a whole. But a user who calls script.get_text() is working from a different definition of 'text' than a user who calls div.get_text()--otherwise there would be no need to call script.get_text() at all. In 4.10.0, the contents of (e.g.) a <script> tag are considered 'text' during a get_text() call on the tag itself, but not considered 'text' during a get_text() call on the tag's parent. Because of this change, calling get_text() on each child of a tag may now return a different result than calling get_text() on the tag itself. That's because different tags now have different understandings of what counts as 'text'. [bug=1906226] [bug=1868861] * NavigableString and its subclasses now implement the get_text() method, as well as the properties .strings and .stripped_strings. These methods will either return the string itself, or nothing, so the only reason to use this is when iterating over a list of mixed Tag and NavigableString objects. [bug=1904309] * The 'html5' formatter now treats attributes whose values are the empty string as HTML boolean attributes. Previously (and in other formatters), an attribute value must be set as None to be treated as a boolean attribute. In a future release, I plan to also give this behavior to the 'html' formatter. Patch by Isaac Muse. [bug=1915424] * The 'replace_with()' method now takes a variable number of arguments, and can be used to replace a single element with a sequence of elements. Patch by Bill Chandos. [rev=605] * Corrected output when the namespace prefix associated with a namespaced attribute is the empty string, as opposed to None. [bug=1915583] * Performance improvement when processing tags that speeds up overall tree construction by 2%. Patch by Morotti. [bug=1899358] * Corrected the use of special string container classes in cases when a single tag may contain strings with different containers; such as the <template> tag, which may contain both TemplateString objects and Comment objects. [bug=1913406] * The html.parser tree builder can now handle named entities found in the HTML5 spec in much the same way that the html5lib tree builder does. Note that the lxml HTML tree builder doesn't handle named entities this way. [bug=1924908] * Added a second way to pass specify encodings to UnicodeDammit and EncodingDetector, based on the order of precedence defined in the HTML5 spec, starting at: https://html.spec.whatwg.org/multipage/parsing.html#parsing-with-a-known-character-encoding Encodings in 'known_definite_encodings' are tried first, then byte-order-mark sniffing is run, then encodings in 'user_encodings' are tried. The old argument, 'override_encodings', is now a deprecated alias for 'known_definite_encodings'. This changes the default behavior of the html.parser and lxml tree builders, in a way that may slightly improve encoding detection but will probably have no effect. [bug=1889014] * Improve the warning issued when a directory name (as opposed to the name of a regular file) is passed as markup into the BeautifulSoup constructor. [bug=1913628] Signed-off-by: Zang Ruochen <[email protected]> Signed-off-by: Khem Raj <[email protected]> Signed-off-by: Trevor Gamblin <[email protected]>

plumdog added bug Needs Triage Issues that need to be evaluated for severity and status. labels Sep 6, 2021

plumdog changed the title ~~[BUG] Should Fail hard when installing packages that want 2to3~~ [BUG] Should fail hard when installing packages that want 2to3 Sep 6, 2021

jaraco mentioned this issue Sep 6, 2021

Fail fast when use_2to3 is supplied. #2770

Merged

jaraco closed this as completed in #2770 Sep 6, 2021

ahnitz mentioned this issue Sep 6, 2021

cannot be installed with latest setuptools ligovirgo/dqsegdb#79

Closed

edgarrmondragon mentioned this issue Sep 7, 2021

Pin setuptools<58.0.0 edgarrmondragon/tap-bitso#16

Merged

serenecloud mentioned this issue Sep 7, 2021

Unable to install with setuptools 58 - "error in jsmin setup command: use_2to3 is invalid." tikitu/jsmin#33

Closed

aaronsteers mentioned this issue Sep 7, 2021

Failing install with latest setuptools (fails due to use_2to3 no longer supported) danthedeckie/simpleeval#90

Closed

maudetes mentioned this issue Sep 7, 2021

Le build échoue depuis setuptools 58.0.2 datagouv/data.gouv.fr#508

Closed

mattclay mentioned this issue Sep 7, 2021

[2.9] Import sanity tests on Python 3.8 always fail ansible/ansible#75647

Closed

1 task

webknjaz removed the Needs Triage Issues that need to be evaluated for severity and status. label Sep 7, 2021

jimmyhli mentioned this issue Sep 7, 2021

[BUG] error in XXXX setup command: use_2to3 is invalid when false. #2775

Closed

1 task

cyface mentioned this issue Sep 7, 2021

suds-jurko dependency fails with Python Setuptools 58.0.2+ BingAds/BingAds-Python-SDK#191

Closed

plumdog mentioned this issue Sep 7, 2021

Do not error if use_2to3 is set to a false value #2777

Merged

2 tasks

Panaetius mentioned this issue Sep 8, 2021

Remove (soft)dependency on rdflib_jsonld RDFLib/pySHACL#93

Closed

neutrinoceros mentioned this issue Sep 8, 2021

MNT: bump minimal required IPython version from 1.0.0 to 2.0.0 yt-project/yt#3505

Merged

Panaetius mentioned this issue Sep 8, 2021

rdflib_jsonld breaks install, replace with RDFLib 6.0 integrated version RDFLib/OWL-RL#45

Closed

jeffzi mentioned this issue Sep 8, 2021

Add support for empty data type annotation in SchemaModel unionai-oss/pandera#602

Merged

thathert mentioned this issue Sep 9, 2021

Troposphere library "AttributeError" fix and python3.9 runtime support zappa/Zappa#1030

Closed

ajnelson-nist mentioned this issue Sep 10, 2021

Outroduction of rdflib-jsonld RDFLib/rdflib#1405

Closed

BryceStevenWilley mentioned this issue Sep 20, 2021

Removed rdflib-jsonld as a dependency scrapinghub/extruct#182

Closed

kpawar-sap added a commit to sapcc/requirements that referenced this issue Sep 22, 2021

Cap setuptools<58.0.0

a2fe6fa

setuptools 58.0.0 and above fails to install due to issue pypa/setuptools#2769

kpawar-sap mentioned this issue Sep 22, 2021

Cap setuptools<58.0.0 sapcc/requirements#36

Merged

kpawar-sap added a commit to sapcc/requirements that referenced this issue Sep 22, 2021

Do not use setuptools > 58.0.0

58872cf

Due to bug pypa/setuptools#2769

kpawar-sap added a commit to sapcc/loci that referenced this issue Sep 22, 2021

Restrict setuptools to < 58.0.0

9723a56

Due to bug pypa/setuptools#2769

kpawar-sap added a commit to sapcc/loci that referenced this issue Sep 22, 2021

Restrict setuptools to < 58.0.0

e87dd8f

Due to bug pypa/setuptools#2769

honzajavorek added a commit to juniorguru/junior.guru that referenced this issue Sep 23, 2021

pin setuptools, see pypa/setuptools#2769

d5801f2

robertbruntz mentioned this issue Oct 13, 2021

Rebase from upstream, remove Python 2 from CI, and set use_2to3=False ligovirgo/dqsegdb#81

Merged

adamnovak mentioned this issue Nov 16, 2021

setuptools and use_2to3 ComparativeGenomicsToolkit/cactus#599

Closed

tokeefe added a commit to harvard-nrg/anatqc that referenced this issue Dec 8, 2021

Dockerfile update, pin pipenv due to pypa/pipenv#4865, setuptools due…

39a72ac

… to pypa/setuptools#2769

n1ngu mentioned this issue Feb 3, 2022

Drop 2to3 setup option calidae/authentication-dummy#7

Merged

Carthaca pushed a commit to sapcc/requirements that referenced this issue Apr 12, 2022

Cap setuptools<58.0.0

dc2db50

setuptools 58.0.0 and above fails to install due to issue pypa/setuptools#2769

Carthaca pushed a commit to sapcc/requirements that referenced this issue Apr 12, 2022

Do not use setuptools > 58.0.0

bf1c73d

Due to bug pypa/setuptools#2769

MeltyBot mentioned this issue May 29, 2022

SDK-based package installation failing due to simpleeval dependency meltano/sdk#212

Closed

This was referenced Aug 26, 2022

Cannot install with setuptools>=58.0.2 python-fedex-devs/python-fedex#169

Closed

Cannot install with setuptools>=58.0.2 Affirm/suds-jurko#7

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG] Should fail hard when installing packages that want 2to3 #2769

[BUG] Should fail hard when installing packages that want 2to3 #2769

plumdog commented Sep 6, 2021 •

edited

Loading

jaraco commented Sep 6, 2021

arpheno commented Sep 7, 2021

ikapelyukhin commented Sep 7, 2021

plumdog commented Sep 7, 2021

mattclay commented Sep 7, 2021

plumdog commented Sep 7, 2021

ajnelson-nist commented Oct 1, 2021

[BUG] Should fail hard when installing packages that want 2to3 #2769

[BUG] Should fail hard when installing packages that want 2to3 #2769

Comments

plumdog commented Sep 6, 2021 • edited Loading

setuptools version

Python version

OS

Additional environment information

Description

Expected behavior

How to Reproduce

Output

Code of Conduct

jaraco commented Sep 6, 2021

arpheno commented Sep 7, 2021

ikapelyukhin commented Sep 7, 2021

plumdog commented Sep 7, 2021

mattclay commented Sep 7, 2021

plumdog commented Sep 7, 2021

ajnelson-nist commented Oct 1, 2021

plumdog commented Sep 6, 2021 •

edited

Loading