-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Consider migrating from pcre to pcre2 #23668
Comments
side note: ubuntu 24.04 doesn't seem to ship |
This is an excellent opportunity to deprecate the re module and recommend a library instead, such as https://github.com/nitely/nim-regex (this way the library can be updated without waiting months for a release and getting hit by other unrelated changes) |
Well, part of Nim depends on regexes itself. I took a quick look over the code base and discovered two such places in Nim itself: |
actually it does not - some packages are depended upon and downloaded to a special |
+1 to deprecate it and to use an external package. I don't mind to have it in the std. The issue I see is the lib dep |
also, |
Did you get a chance to work on it? Nim has been out of debian testing for a while by now due to this being a release critical bug for us (pcre3) not being a part of next release. |
FWIW I found no migration guide. |
fwiw, there is this PCRE2Project/pcre2#51 (comment) and the linked PRs as migration examples. |
Description
Nim depends on the obsolete PCRE library, which is no longer supported with last release in 2021, and should migrate to PCRE2 library available since 2015.
I am concerned that Debian wants to remove the deprecated PCRE library (see this bug report), making some of the functionality and some of the Nim packages unusable in the next stable Debian release.
So, please consider porting
std/nre
andstd/re
to PCRE2. PCRE and PCRE2 seem to be API incompatible, but it should not be a problem for anyone who doesn't use the C wrappers directly.Nim Version
Any version at the time of writing (
devel
branch is affected as ofcdfc886f88cc95a8dc05e2211d1030b146a521f5
)Current Output
No response
Expected Output
No response
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: