Skip to content

Tests fail: TypeError: Tried to dispatch on non-type: [<class 'object'>] #24

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

Closed
yurivict opened this issue Jun 21, 2023 · 5 comments
Closed

Comments

@yurivict
Copy link

============================================================================================================ ERRORS ============================================================================================================
_____________________________________________________________________________________________ ERROR collecting tests/test_core.py ______________________________________________________________________________________________
tests/test_core.py:7: in <module>
    from etuples.core import ExpressionTuple, InvalidExpression, KwdPair, etuple
etuples/__init__.py:2: in <module>
    from .core import etuple
etuples/core.py:343: in <module>
    def etuple(*args, **kwargs):
/usr/local/lib/python3.9/site-packages/multipledispatch/core.py:68: in _
    dispatcher.add(types, func, on_ambiguity=on_ambiguity)
/usr/local/lib/python3.9/site-packages/multipledispatch/dispatcher.py:133: in add
    raise TypeError("Tried to dispatch on non-type: %s\n"
E   TypeError: Tried to dispatch on non-type: [<class 'object'>]
E   In signature: <[<class 'object'>]>
E   In function: etuple
___________________________________________________________________________________________ ERROR collecting tests/test_dispatch.py ____________________________________________________________________________________________
tests/test_dispatch.py:6: in <module>
    from etuples.core import ExpressionTuple, KwdPair, etuple
etuples/__init__.py:2: in <module>
    from .core import etuple
etuples/core.py:343: in <module>
    def etuple(*args, **kwargs):
/usr/local/lib/python3.9/site-packages/multipledispatch/core.py:68: in _
    dispatcher.add(types, func, on_ambiguity=on_ambiguity)
/usr/local/lib/python3.9/site-packages/multipledispatch/dispatcher.py:133: in add
    raise TypeError("Tried to dispatch on non-type: %s\n"
E   TypeError: Tried to dispatch on non-type: [<class 'object'>]
E   In signature: <[<class 'object'>]>
E   In function: etuple
======================================================================================================= warnings summary =======================================================================================================
../../../../../local/lib/python3.9/site-packages/multipledispatch/core.py:79
../../../../../local/lib/python3.9/site-packages/multipledispatch/core.py:79
  /usr/local/lib/python3.9/site-packages/multipledispatch/core.py:79: DeprecationWarning: inspect.getargspec() is deprecated since Python 3.0, use inspect.signature() or inspect.getfullargspec()
    spec = inspect.getargspec(func)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
================================================================================================ 2 warnings, 2 errors in 0.78s =================================================================================================

Version: 0.3.9
Python-3.9
FreeBSD 13.2

@brandonwillard
Copy link
Member

I see that you've linked to here from an issue in a fork of Aesara (i.e. pytensor); just so you know, these Pythological and Aesara projects are not associated with that fork and/or those developers.

@brandonwillard
Copy link
Member

brandonwillard commented Jun 22, 2023

I can't reproduce this issue locally, so I created #25 to update some things in the project and to help determine if this issue has anything to do with our local setups.

@brandonwillard
Copy link
Member

Again, it looks like your environment may be the cause of those issues.

@brandonwillard brandonwillard closed this as not planned Won't fix, can't repro, duplicate, stale Jun 22, 2023
@yurivict
Copy link
Author

But what's wrong with the environment?
Virtually all python packages build fine in this environment.

@brandonwillard
Copy link
Member

But what's wrong with the environment? Virtually all python packages build fine in this environment.

How exactly is the environment being constructed? Can you provide a MWE?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants