Xavier Deguillard d89eab8078 pyconfigparser: use String as arguments instead of PyBytes ... Summary: In the cpython bindings, the Rust String can take both PyBytes and PyUnicode strings, which is perfect for Python3 compatibility as string literals are PyBytes in Python2 and PyUnicode in Python3. The return values are kept as Bytes for now as changing this is a much larger change in itself. Other approaches tried: - Using PyUnicode as input/output: an extremely large codemod had to be done, with very little benefits - Using String as output: since we do have some configs that are unicode, on the Python side, the output might either be bytestrings or unicode, leading to weird bugs. Reviewed By: DurhamG Differential Revision: D18650466 fbshipit-source-id: aebdf30590dcae40b7df2787e5ece88e2ec9395c		2020-01-16 09:31:45 -08:00
..
benches	Move fb-mercurial sources into an eden/scm subdirectory.	2019-11-13 16:04:48 -08:00
src	pyconfigparser: use String as arguments instead of PyBytes	2020-01-16 09:31:45 -08:00
Cargo.toml	Switch from failure::Fail trait to std::error::Error for errors	2019-11-22 08:53:31 -08:00
CMakeLists.txt	Merge fb-mercurial sources into the eden repository	2019-11-13 20:20:32 -08:00
ConfigParser.cpp	Merge fb-mercurial sources into the eden repository	2019-11-13 20:20:32 -08:00
ConfigParser.h	Move fb-mercurial sources into an eden/scm subdirectory.	2019-11-13 16:04:48 -08:00