Skip to content
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

PavlovaParsingError: Field: consent missing on dt.iab_chair().name #126

Open
sbenthall opened this issue Aug 16, 2023 · 5 comments
Open

Comments

@sbenthall
Copy link

Running this code from the examples/ directory in a local notebook in an environment with ietfdata installed using pip install -U ietfdata:

from datetime                 import timedelta
from pathlib                  import Path
from ietfdata.datatracker     import *
from ietfdata.datatracker_ext import *
from dateutil.parser          import *

dt = DataTrackerExt()

# =============================================================================
# Information about the IAB:

print(F"The IAB chair is {dt.iab_chair().name}")

print("The IAB members are:")
for m in dt.iab_members():
    print(F"  {m.name}")
print("")

I'm getting the following error/stack trace:
https://gist.github.com/sbenthall/688b3e9fb920e0f1f7ec212718a491a0

I wonder if there's been an API change, or if I've mistaken the configuration/installation somehow.

@lumisota
Copy link
Member

Which version of the library are you using? The consent field for the person endpoint was removed a while ago (~October 2022), I think.

@sbenthall
Copy link
Author

Thank you. I was using version 6.0. I determined that this was because my Python environment was running Python 3.8. I've now updated the environment to use Python 3.7. I am now using ietfdata version 0.6.7.

Now I get a different error: KeyError: typing.Optional

https://gist.github.com/sbenthall/5179ad535052685f849cb36af25d6e11

@lumisota
Copy link
Member

It looks like you're using Python 3.10, which I think makes changes to typing hints, so there might be refactoring needed to support that. I'll take a look.

In the meantime, the library should work with 3.9.

@sbenthall
Copy link
Author

Aha. That does sound right. Thanks. I'll switch to 2.9 for now.

@lumisota
Copy link
Member

Thanks; have added #128 -- will look at support for more recent Python versions.

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