Patch number 3! > From 0c62b541a3e8925b5ca31fe55dbe7536cf95151f Mon Sep 17 00:00:00 2001 > From: Maxim Cournoyer <[email protected]> > Date: Thu, 28 Mar 2019 00:26:01 -0400 > Subject: [PATCH 3/9] import: pypi: Improve parsing of requirement > specifications. > > The previous solution was fragile and could leave unwanted characters in a > requirement name, such as '[' or ']'.
Wouldn’t it be sufficient to add [ and ] to the list of forbidden characters? The tests pass with this implementation of clean-requirements: (define (clean-requirements s) (cond ((string-index s (char-set #\space #\> #\= #\< #\[ #\])) => (cut string-take s <>)) (else s))) > +(define %requirement-name-regexp > + ;; Regexp to match the requirement name in a requirement specification. > + > + ;; Some grammar, taken from PEP-0508 (see: > + ;; https://www.python.org/dev/peps/pep-0508/). > + > + ;; The unified rule can be expressed as: > + ;; specification = wsp* ( url_req | name_req ) wsp* > + > + ;; where url_req is: > + ;; url_req = name wsp* extras? wsp* urlspec wsp+ quoted_marker? > + > + ;; and where name_req is: > + ;; name_req = name wsp* extras? wsp* versionspec? wsp* quoted_marker? > + > + ;; Thus, we need only matching NAME, which is expressed as: > + ;; identifer_end = letterOrDigit | (('-' | '_' | '.' )* letterOrDigit) > + ;; identifier = letterOrDigit identifier_end* > + ;; name = identifier > + (let* ((letter-or-digit "[A-Za-z0-9]") > + (identifier-end (string-append "(" letter-or-digit "|" > + "[-_.]*" letter-or-digit ")")) > + (identifier (string-append "^" letter-or-digit identifier-end "*")) > + (name identifier)) > + (make-regexp name))) This seems a little too complicated. Translating a grammar into a regexp is probably not a good idea in general. Since we don’t care about anything other than the name it seems easier to just chop off the string tail as soon as we find an invalid character. -- Ricardo
