-
-
Notifications
You must be signed in to change notification settings - Fork 570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyrsistent no longer supports Python2.7 #741
Comments
Any suggestion of a workaround? Can I force a pyrsistent version for jsonschema dependency? Also, I'm a bit confused....how could you say that jsonschema supports python2.7 when one of its dependencies definitely does not? |
You should always be pinning your dependencies in wherever you're using jsonschema, for exactly this scenario (where a transitive dependency has a bug and forgets to do something or other and it breaks your app) |
OK, I'll give that a shot. Thank you! |
54f3784a8 Merge pull request #731 from MeastroZI/main ff29264c2 Merge pull request #741 from harrel56/chore/tabs-to-spaces 9f39cf731 use spaces instead of tabs 2f3b5f7ab Corrected replaced unevaluated with additoinalProperties fa9224d7e Merge pull request #732 from MeastroZI/main2 83bedd5c8 Changing descriptions 49f73429c fixing tests e6d6a0816 adding more test cases 7e6c9be6d changing descriptions 959aca926 shifting test 605d7d786 Update propertyDependencies.json : test must be tests deb82824b test for dependentSchema and propertyDependencies with unevaluatedProperties and additionalProperties ea4851242 Merge branch 'json-schema-org:main' into main 64a3e7b37 Merge pull request #721 from json-schema-org/gregsdennis/dynamicref-skips-resources b9f14e64c Fix $schema in new new test 3d5048e83 Merge pull request #733 from Era-cell/main 2480edbae Update additionalProperties.json formatting it 6aa79c0b2 Update additionalProperties.json formatting it 3e0139a54 Update tests/draft-next/additionalProperties.json 616240b06 Update tests/draft-next/additionalProperties.json c5f3e4eaa Update tests/draft2020-12/propertyNames.json 964efb8e6 propertyNames doesn't affect additionalProperties, tests exist already for unevaluatedProps f08b884cf Cases go under additional and unevaluated Properties 99864ff66 added tests for propertyNames with additionalProperties/unevaluatedProperties, also with specification property 3b5782b65 Update ref.json : changing $Ids 546b3561a test for $ref with $recursiveAnchor 57617f254 Merge pull request #726 from Era-cell/main 51fc69cd7 meta data and property names constraints added, additional Items: string 9b169bed8 specification takes array of objects having section and quote 1362a8cce Pattern for para corrected 340116ecf Schema of specification in much structured 003ac0211 Test-schema including sub-schema for scpecification 50a20280b adding specification enhancement for additionalProperties 604f5f99b Drop tests of `$id` and `$anchor` that just test values against meta-schema `pattern` for those properties 9cd64ec94 come on man, save all the files f494440e3 use unique $id in optional tests, too 468453b0f use unique $id 9ec6d17e7 fix copy/paste error b284f4232 add tests for $dynamicRef skipping over resources bf0360f4b add $recursiveAnchor to 2019-09 meta-schemas 0519d1f0e add $dynamicAnchor to meta-schemas git-subtree-dir: json git-subtree-split: 54f3784a8c6926d8e91ed43267950a07efc34086
As of September 8, 2020, the jsonschema package no longer supports Python2.7, but not because of code it contributed, but because of a restriction placed on a dependent package (Pyrsistent). As of the aformentioned date, Pyrsistent no longer supports a Python version < 3.5 ( https://github.com/tobgu/pyrsistent/blob/ccc4a341ea74f80df8487654bfc7c638865867d4/setup.py#L81 ).
This would be fine and dandy, except for the way jsonschema defines dependencies, meaning I could pull an older version of jsonschema, but when it resolves its dependencies, it'll pull the most recent version of Pyrsistent (as seen in the setup.cfg of version as far back as Jan, 2019 - https://github.com/Julian/jsonschema/blob/21838cd7727bd7c1d9a309df51cd32ebb0c78cdb/setup.cfg#L28 ).
I get that Python2.7 is no longer supported, but I would expect older versions that previously worked on Python2.7 to continue to work on Python2.7.
The text was updated successfully, but these errors were encountered: