NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi all! Just joined this mailing list, and catching up with stuff about pydap and tds. I am actively developing pydap, and updating the documentation. I have migrated the documentation to GitHub pages. And while reading through this thread (and another one about pydap authentication), I was curious about where it said that the username/password could be added to the url . Very interesting approach! I found the source of it, the old pydap documentation. I recently started updating pydap, and its documentation . In the updated Pydap documentation you can find a particular examples on authentication with username, and with tokens as well. The documentation is built using executable notebooks. https://pydap.github.io/pydap/notebooks/Authentication.html I am still curious about adding the username/password to the url. Perhaps internally pydap used to parse that information before my time? I never knew about it... Anyways, I suggest to bring this issue on PyDAP's GitHub repository. And we can continue the conversation there. I also follow the updated documentation (url above). PS - I have updated PyDAP and the new version 3.5 is compatible with numpy >=2.0. Cheers, Miguel
Attachment:
signature.asc
Description: Message signed with OpenPGP
thredds archives: