TypeError: attrib() got an unexpected keyword argument 'converter'

In a Travis CI linux build on Python 3.6, I am getting an odd error:

E   TypeError: attrib() got an unexpected keyword argument 'converter'

The errors occurs in the following line of jsonschema:

https://github.com/Julian/jsonschema/blob/bb92111a85c981d14788257ebc0885f272b17e40/jsonschema/_types.py#L64

Windows builds passed. These builds are for https://github.com/greenelab/manubot/pull/49/commits/34de1a6f34c2b3cc8bc7ee112347a0f6af6a1e99 of https://github.com/greenelab/manubot/pull/49.

Interestingly, the tests pass locally for me on Linux. From the test log, it seems that the error is being triggered upon import. Possibly related to pytest.

[Julian]

Yeah setup.py install hasn’t been a great way to install things for awhile – definitely go for pip. Glad you got it working.

On Wed, Aug 8, 2018, 16:53 Daniel Himmelstein [e-mail] wrote:

Let me wipe the Travis pip cache and rerun.

That did not fix. However, I switched to installing the manubot package on Travis using pip install . rather than python setup.py install in greenelab/manubot@ec10ec6 https://github.com/greenelab/manubot/commit/ec10ec63ff0c7ee038d6efdf9cc7ed859854a2e0. The new Travis build https://travis-ci.org/greenelab/manubot/builds/413590031#L482 passed!

I believe python setup.py install was using easy_install rather than pip, but not sure why this would cause the outdated version of attrs when it claimed to be installing 18.1.0. Anyways, I’m happy since the build is passing, so not likely to dig further unless this issue reappears.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/Julian/jsonschema/issues/449#issuecomment-411413391, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUIXkYaMNkoutNQIg4v7ptbl5bPvZ84ks5uOu1QgaJpZM4Vy-J9 .

[Julian]

@dhimmel jsonschema should already be declaring that it needs attrs>17.4 – just in case that was added after v3.0.0a1, I just pushed a v3.0.0a2, but there’s also a small chance you are depending on some library that is pinning attrs to below 17.4.0.

Try re-running your build now and see if it still fails?

Will close this since jsonschema’s own test suite is passing here so I’m pretty sure the bug would be elsewhere, but leave a comment if you have any issues.