Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[python] always respect typespec namesapce even if package-name is set #5649

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

msyyc
Copy link
Contributor

@msyyc msyyc commented Jan 17, 2025

We have discussed that we shall always respect typespace namespace even if the package-name is different with it.

@microsoft-github-policy-service microsoft-github-policy-service bot added the emitter:client:python Issue for the Python client emitter: @typespec/http-client-python label Jan 17, 2025
@azure-sdk
Copy link
Collaborator

No changes needing a change description found.

@azure-sdk
Copy link
Collaborator

azure-sdk commented Jan 17, 2025

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs 🛝 VSCode Extension

@msyyc msyyc changed the title [python] always respect typespec namesapce even if package-name is set [python] always respect typespec namesapce even if package-name is set (not ready to review) Jan 17, 2025
@msyyc msyyc changed the title [python] always respect typespec namesapce even if package-name is set (not ready to review) [python] always respect typespec namesapce even if package-name is set Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emitter:client:python Issue for the Python client emitter: @typespec/http-client-python
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants