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
Update to a more recent version of nom #92
Comments
Now there are 🙂 More seriously, I've long been aware of the age of that particular dependency, but I've postponed upgrading due to internal One thing that is potentially more involved than upgrading |
Great! Thank you for your reply and for considering our request. 👍 Regarding |
It's a bit more annoying as nom has since version 2 removed some of the partial parsing statekeeping it provided users with (notably |
The The filter part: merged, see 99fd7dd. You can test with the current HEAD, and I'm going to publish a 0.11 beta when I finish a couple of other housekeeping tasks. I'm leaving the issue open until then. |
Fantastic! Thank you very much. I'll give this a try and let you know if I run into any issues. |
0.11-beta has been published; closing this issue. |
Thanks again to both of you for your efforts. I've been testing |
Hey there!
We are currently evaluating
ldap3
because we are interested in using it in Proxmox Backup Server to enable LDAP login for our users. So far, we are pretty happy with it. As we try to keep the number of duplicated/outdated dependencies to a minimum, we were wondering: Are there currently any plans to update to a more recent version ofnom
?Best Regards,
Lukas
The text was updated successfully, but these errors were encountered: