Remko,
thanks a lot for the link, I had a short look at your patch.
For our current plans of switching from Python 2.x to 3.x, the code
changes themselves might not be that helpful right now, because we still
don't know how exactly our Unicode support will look like internally.
But what's important is that we don't forget about this Value issue that
you detected.
So it would help us a lot if you could create a simple testcase for
this, which breaks with the current code but should run successfully in
the end. A single SConstruct is fine, a full testcase according to
"QMTest/test-framework.rst" is better. ;)
When rewriting the core sources towards 3.x we could then use this test
(and others that probably follow) to ensure that things work as expected.
My plan is to open a Wiki page for the whole Unicode conversion, which
would then contain a link to your issue #2910. So if you attach your
testcase there, it won't get forgotten.
Regards,
Dirk
On 13.07.2013 10:30, Remko Tronçon wrote:
Hi Dirk,
On 13 July 2013 10:14, Dirk Bächle <[email protected]> wrote:
Have you tried to actually compile/build stuff that uses Unicode chars in
filenames? Or are you only analyzing the dependencies?
The real problem I have isn't with actually with files, but with
Values() with unicode characters in them (which are also printed
verbatim in the tree).
Can you please attach
your patch to the Tigris tracker issue or point us to the repository, if you
cloned the SCons sources?
https://bitbucket.org/r3mko/scons/commits/1ffc15e2718f03833deaec7f53da5ca67c934d3e
cheers,
Remko
_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev
