> Great! I'll work on it. > > How should we do to avoid compatibility problems? Some solutions that > come into my mind are: > > - Forget about it completely and fix the syntax handling to be > posix compliant. > > - Create a subclass of shlex, or a completely different class > (shlex_posix?) depending on how much can be reused. > > - Add a flag to the constructor. Thinking further about this, I belive there's a better solution. I'll write different functions (probably read_word()/get_word()) with the new behavior. -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4