ID 366574 - Nuke script precision is altered after Denoise node to use Scientific Notation, when it shouldn't

​Problem summary
When saving a Nuke script or copying a Group of nodes, float values gets saved in a format that look like the following - "regionBL {204.8000031 155.6000023}". However when a Denoise node is added before your node, values gets save in a scientific format instead. - "regionBL {2.0480000305e+02 1.5560000232e+02}".

This problem can cause plugins and scripts to fail, because running "to_script" function on a specific knobs returns one thing if the node was created during the current session, but when you save your Nuke script and reopen it, "to_script" returns the scientific notation instead. 

If the node is copied by itself after the Denoise, the issue does not occur..

This issue is regressive with Nuke11.0v1  ( Works as expected on Nuke10.5v7 )

Customer reported version
nuke.11.2v3

Customer reported platform
centos7

Steps to reproduce

1) Create a Grade node and set its 'Multiply' knob to: "123.4567890"

2) Underneath the Grade node, add a Denoise node

3) Copy the Original Grade node from above and connect it below the Denoise node

4) Copy/Paste the nodes into a text editor.

Result: The Multiply value in the Grade node after the Denoise will use Scientific Notation, which is different when compared to the first Grade.
Workaround
When Copying Nodes:
When Saving/Reloading project:

Reproduced by support

This bug has been reproduced in:
Nuke11.2v3 - Windows 7 - Mac10.13 - CentOS6.9
Nuke11.2v3 - Windows 7
Nuke11.1v4 - Windows 7
Nuke11.1v1 - Windows 7 
Nuke11.0v4 - Windows 7
Nuke11.0v1 - Windows 7 - Mac10.13 - CentOS6.9 - Regression
Unable to reproduce bug in:
Nuke10.5v7 - Windows 7 - Mac10.13 - CentOS6.9

Earliest version tested
- This issue no longer appears in this version and has regressed

Expected behaviour
- Nodes copied/saved after a Denoise should not be given scientific notation knob values.

Actual behaviour
- Knob values are changed after a Denoise node, causing errors.