William Deegan
William Deegan
It seems you did not read this "Please bring your issue to the SCons users mailing list before filing an issue here". Please bring your issue to the users mailing...
Please take a look at how I've modified your initial info above. In the future try to format similarly. But of course, please bring the issue to the users mailing...
It seems you did not read this "Please bring your issue to the SCons users mailing list before filing an issue here". Please bring your issue to the users mailing...
probably worth doing at some point.
Probably worth some effort. Though that patch wouldn't really do it. I'd take the Zip() builder and just swap in gzip calls.
The reasons for not doing that are gone. There was a time when we supported pythons which didn't have subprocess (I beleive that was the reason) And then the recommended...
Ahh.. Good question. I think least painful way to enable might be to pass a cwd to the FunctionAction() and then require all such to be updated.. Changing to `multiprocessing`...
That said, a PR which addresses only command actions would still move the ball forward right?
The problem is since subprocesses are running in threads, and all threads share the same CWD.. if any other command runs from another thread, it'll be in the wrong directory....
> Turns out from a different set of work (see #3920) that the filesystem tool itself is also undocumented. This issue goes on to suggest some consolidation... any thoughts on...