[Rana Singh (ranadeepsingh)]

Generated Python stubs can retain a method definition overwritten by a later definition, and service-column alias checks can miss equivalent Unicode identifiers or continued declarations. This follow-up corrects supported def-based stub extraction and method-definition collision checks.

Related Issues/PRs

Follow-up to #2810 and #2805.

What changes are proposed in this pull request?

• Keep the effective final unconditional def binding when generating supported stubs.
• Normalize identifier identity with Python's NFKC rules for service-alias collision checks.
• Handle explicit continuations, descriptor decorators, nested scopes, async declarations, and Python indentation; retain the existing ASCII-only supported stub-signature boundary.

Existing scope limits: extraction tracks method definitions, not arbitrary Python class-attribute rebinding. Assignments (including method = classmethod(method)), annotated assignments, nested classes, del, and imports can still leave stale method stubs or bypass service-alias collision checks. Those limitations exist on the target branch and are not fixed here. Generated additional methods should use explicit def declarations and supported decorators rather than those rebinding forms. Quoted annotations containing = also retain the existing stub-parsing limitation.

How is this patch tested?

Local validation covers the pending source corrections based on master 6c2699defcfb24d5bff5ba55f2252ba2d8cbea24. Those corrections are not yet all in the published PR head.

sbt "set core / Test / fork := false" "core/compile" "core/Test/compile" "core/testOnly com.microsoft.azure.synapse.ml.codegen.PyCodegenSuite" "core/scalastyle" "core/Test/scalastyle"

Passed: compile, test compilation, 97/97 tests (0 skipped), production scalastyle, and test scalastyle. Run with JDK 11, Spark 3.5.0, Scala 2.12.17, Python 3.11.8, and a single test JVM.

Draft status: local regression gates passed. The six-round review process, publication and Azure/GitHub CI for the latest pending source, and remote-comment reconciliation are not yet complete. Published as a draft first with explicit approval so review evidence can use the real PR number; no readiness gate is waived.

• I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

• No. You can skip this section.
• Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

• No. You can skip this section.
• Yes. Make sure you have added samples following below steps.

1. Find the corresponding markdown file for your new feature in website/docs/documentation folder.
   Make sure you choose the correct class estimators/transformers and namespace.
2. Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
3. Make sure the DocTable points to correct API link.
4. Navigate to website folder, and run npm start to make sure the website renders correctly.
5. Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
6. Make sure the WebsiteSamplesTests job pass in the pipeline.

[github-actions]

Hey Rana Singh (@ranadeepsingh) 👋!
Thank you so much for contributing to our repository 🙌.
Someone from SynapseML Team will be reviewing this pull request soon.

We use semantic commit messages to streamline the release process.
Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix.
This helps us to create release messages and credit you for your hard work!

Examples of commit messages with semantic prefixes:

• fix: Fix LightGBM crashes with empty partitions
• feat: Make HTTP on Spark back-offs configurable
• docs: Update Spark Serving usage
• build: Add codecov support
• perf: improve LightGBM memory usage
• refactor: make python code generation rely on classes
• style: Remove nulls from CNTKModel
• test: Add test coverage for CNTKModel

To test your commit locally, please follow our guild on building from source.
Check out the developer guide for additional guidance on testing your change.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Rana Singh (ranadeepsingh)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).