Inconsistent Behavior with cmds.polyEditUV Query Mode

[martin.svardZ96DQ]

I would like to report a potential bug with the cmds.polyEditUV command in Autodesk Maya 2024.2. When using this command in query mode with the vValue flag, it unexpectedly returns both U and V values, rather than just V values as one would expect based on the documentation.

Steps to reproduce:

1. Select some UVs on a polygonal mesh.
2. Run the following command: cmds.polyEditUV(query=True, vValue=True)

Expected behavior:
The command should return only the V values of the selected UVs.

Actual behavior:
It returns both U and V values, which is not consistent with the documentation or expected usage. Based on the documentation, using vValue=True in query mode should return only V coordinates, similar to how uValue=True behaves when querying U coordinates.

I believe this behavior is unintended, and it would be great if this could be addressed or clarified in future updates or documentation.

Thank you for your attention to this matter.

[FirespriteNate]

If I remember correctly, this command has had this behaviour since at least Maya 8.5, if not before (probably always, it's just I only started scripting seriously from about 8.5).

They probably can't actually fix it now, otherwise about 20 years of scripts would just stop working 😄 

However, as you mention, it's annoying that the docs are not representative of the actual behaviour, so at very least it would be nice if they updated the docs to fit.

[martin.svardZ96DQ]

I definitely agree with you—changing functionality isn’t ideal, as it would break a lot of existing scripts.

That said, while I understand the need to preserve backward compatibility, new functions could be introduced that behave as expected, with the older ones gradually deprecated over time. This approach would allow Autodesk to maintain compatibility while also evolving the API for future use.

In the meantime, updating the documentation to accurately reflect the current behavior would be a great first step. It would help prevent confusion and ensure that developers, especially newer users, understand what to expect from cmds.polyEditUV and avoid falling into this trap.