Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.8.0 RC, 5.15.6, 6.2.0
-
None
-
8
-
5fc9c02a695edca23c0f8b2ec4c258e2c4212ea8 (qt/qtbase/dev)
-
Team 1 Foundation_Sprint 45, Team 2 Foundation_Sprint 46
Description
With:
QProcess p; p.setProcessEnvironment(QProcessEnvironment()); p.start();
... in the child process, you'll still end up with a copy of the system environment.
I'm not sure if this is deliberate (maybe it is, since the default QProcessEnvironment is "empty", and that's used to say "copy the system environment"), but it should be fixed in docs if so, as right now it's ambiguous:
If no environment has been set, the environment of the calling process will be used.
... to me, implies that the requirement is to call setProcessEnvironment with an environment of my choice, even if I choose it to be empty.