Future: Python 3.8 compatibility
See original GitHub issueThis warning will need to be addressed in the future, as it would break in Python 3.8:
spiceypy/tests/test_spiceerrors.py::test_getSpiceyException
/Users/klay6683/Dropbox/src/SpiceyPy/spiceypy/utils/support_types.py:107: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
return isinstance(i, collections.Iterable) and not isinstance(i, six.string_types)
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
__future__ — Future statement definitions — Python 3.11 ...
To document when incompatible changes were introduced, and when they will be — or were — made mandatory. This is a form of...
Read more >future - PyPI
Project description. future is the missing compatibility layer between Python 2 and Python 3. It allows you to use a single, clean Python...
Read more >Quick-start guide — Python-Future documentation
To offer backward compatibility with Python 2 from your Python 3 code, you can use the pasteurize script. This adds these lines at...
Read more >What is __future__ in Python used for and how/when to use it ...
The future statement is intended to ease migration to future versions of Python that introduce incompatible changes to the language. It allows ...
Read more >__future__ Module in Python - GeeksforGeeks
__future__ module is a built-in module in Python that is used to inherit new features that will be available in the new Python...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@michaelaye I had mixed up if it does the Python 3 or Python 2 first. The warning shouldn’t occur because the Python 3 approach succeeds.
six is also a very popular and small dependency, I don’t plan on ever removing it from the package unless forced