update readmes (#3498)

Author: iscai-msft

README.md

@@ -1,62 +1,3 @@
 # Python Generator Packages
 
-## Requirements
-
--   Node 20+
--   pnpm 9+
--   Python 3.9+
-
-## Develop
-
-This project uses [pnpm workspaces](https://pnpm.io/workspaces) to manage multiple packages.
-
-```bash
-pnpm install
-```
-
-2. Build
-
-```bash
-pnpm build
-```
-
-3. Build TS in watch mode
-
-```bash
-pnpm watch
-```
-
-4. Clean
-
-```bash
-pnpm clean
-```
-
-## Release a new version
-
-**Semi-auto:**
-
-Follow https://github.com/Azure/autorest.python/blob/main/.github/skills/bump-and-release/SKILL.md to make a release PR. 
-After it merged, [release pipeline](https://dev.azure.com/azure-sdk/internal/_build?definitionId=1668) will be triggered automatically to release new version.
-
-## Contributing
-
-This project welcomes contributions and suggestions. Most contributions require you to agree to a
-Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
-the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
-
-When you submit a pull request, a CLA bot will automatically determine whether you need to provide
-a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
-provided by the bot. You will only need to do this once across all repos using our CLA.
-
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
-For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
-contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
-
-## Trademarks
-
-This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft
-trademarks or logos is subject to and must follow
-[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
-Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
-Any use of third-party trademarks or logos are subject to those third-party's policies.
+**This repo is deprecated, the unbranded emitter `@azure-tools/typespec-python` has moved [here](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-python) and the `autorest.python` emitter is no longer supported**

packages/autorest.python/README.md

@@ -1,25 +1,6 @@
 # Generating with Autorest for Python
 
-See [here](https://github.com/Azure/autorest.python/wiki/Generating-with-autorest-for-python-v5.0.0) for Python-specific docs, and [here] for general docs
-
-# Contributing
-
-This project welcomes contributions and suggestions. Most contributions require you to agree to a
-Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
-the rights to use your contribution. For details, visit https://cla.microsoft.com.
-
-When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
-a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
-provided by the bot. You will only need to do this once across all repos using our CLA.
-
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
-For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
-contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
-
-### Autorest plugin configuration
-
-- Please don't edit this section unless you're re-configuring how the powershell extension plugs in to AutoRest
-  AutoRest needs the below config to pick this up as a plug-in - see https://github.com/Azure/autorest/blob/master/docs/developer/architecture/AutoRest-extension.md
+**This emitter is deprecated and will no longer receive support**
 
 #### Python code gen
 
@@ -138,33 +119,6 @@ scope-multiclientscript/emitter:
 output-artifact: python-files
 ```
 
-# Help
-
-```yaml
-help-content:
-  python: # type: Help as defined in autorest-core/help.ts
-    activationScope: python
-    categoryFriendlyName: Python Generator
-    settings:
-      - key: python-sdks-folder
-        description: The path to the root directory of your azure-sdk-for-python clone. Be sure to note that we include `sdk` in the folder path.
-      - key: black
-        description: Runs black formatting on your generated files. Defaults to `false`.
-        type: string
-      - key: basic-setup-py
-        description: Whether to generate a build script for setuptools to package your SDK.  Defaults to `false`, generally not suggested if you are going to wrap the generated code
-        type: bool
-      - key: no-namespace-folders
-        description: Specify if you don't want pkgutil-style namespace folders. Defaults to `false`.
-        type: bool
-      - key: credential-default-policy-type
-        description: Specify the default credential policy (authentication policy) for your client. Use in conjunction with `--add-credential`. Currently only supports `BearerTokenCredentialPolicy`, `ARMChallengeAuthenticationPolicy` and `AzureKeyCredentialPolicy`. Default value is `BearerTokenCredentialPolicy`(data-plan)/`ARMChallengeAuthenticationPolicy`(mgmt-plan). `--credential-scopes` is tied with `BearerTokenCredentialPolicy` and `ARMChallengeAuthenticationPolicy`, do not pass them in if you want `AzureKeyCredentialPolicy`.
-        type: string
-      - key: credential-key-header-name
-        description: The name of the header which will pass the credential. Use if you have `--credential-default-policy-type` set to `AzureKeyCredentialPolicy`. For example, if generating cognitive services code, you might use `--credential-key-header-name=Ocp-Apim-Subscription-Key`
-        type: string
-```
-
 <!-- LINKS -->
 
 [python_docs]: https://github.com/Azure/autorest.python/tree/main/docs/readme.md

packages/typespec-python/README.md

@@ -1,139 +1,3 @@
 # @azure-tools/typespec-python
 
-TypeSpec emitter for Python SDKs
-
-## Install
-
-```bash
-npm install @azure-tools/typespec-python
-```
-
-## Usage
-
-1. Via the command line
-
-```bash
-tsp compile . --emit=@azure-tools/typespec-python
-```
-
-2. Via the config
-
-```yaml
-emit:
-    - "@azure-tools/typespec-python"
-```
-
-The config can be extended with options as follows:
-
-```yaml
-emit:
-    - "@azure-tools/typespec-python"
-options:
-    "@azure-tools/typespec-python":
-        option: value
-```
-
-## Emitter options
-
-### `emitter-output-dir`
-
-**Type:** `absolutePath`
-
-Defines the emitter output directory. Defaults to `{output-dir}/@azure-tools/typespec-python`
-See [Configuring output directory for more info](https://typespec.io/docs/handbook/configuration/configuration/#configuring-output-directory)
-
-### `examples-dir`
-
-**Type:** `string`
-
-Specifies the directory where the emitter will look for example files. If the flag isn’t set, the emitter defaults to using an `examples` directory located at the project root.
-
-### `namespace`
-
-**Type:** `string`
-
-Specifies the namespace you want to override for namespaces set in the spec. With this config, all namespace for the spec types will default to it.
-
-### `flavor`
-
-**Type:** `string`
-
-The flavor of the SDK.
-
-### `models-mode`
-
-**Type:** `"dpg" | "none"`
-
-What kind of models to generate. If you pass in `none`, we won't generate models. `dpg` models are the default models we generate.
-
-### `generate-sample`
-
-**Type:** `boolean`
-
-Whether to generate sample files, for basic samples of your generated sdks. Defaults to `false`.
-
-### `generate-test`
-
-**Type:** `boolean`
-
-Whether to generate test files, for basic testing of your generated sdks. Defaults to `false`.
-
-### `api-version`
-
-**Type:** `string`
-
-Use this flag if you would like to generate the sdk only for a specific version. Default value is the latest version. Also accepts values `latest` and `all`.
-
-### `license`
-
-**Type:** `object`
-
-License information for the generated client code.
-
-### `package-version`
-
-**Type:** `string`
-
-The version of the package.
-
-### `package-name`
-
-**Type:** `string`
-
-The name of the package.
-
-### `generate-packaging-files`
-
-**Type:** `boolean`
-
-Whether to generate packaging files. Packaging files refer to the `setup.py`, `README`, and other files that are needed to package your code.
-
-### `packaging-files-dir`
-
-**Type:** `string`
-
-If you are using a custom packaging files directory, you can specify it here. We won't generate with the default packaging files we have.
-
-### `packaging-files-config`
-
-**Type:** `object`
-
-If you are using a custom packaging files directory, and have additional configuration parameters you want to pass in during generation, you can specify it here. Only applicable if `packaging-files-dir` is set.
-
-### `package-pprint-name`
-
-**Type:** `string`
-
-The name of the package to be used in pretty-printing. Will be the name of the package in `README` and pprinting of `setup.py`.
-
-### `head-as-boolean`
-
-**Type:** `boolean`
-
-Whether to return responses from HEAD requests as boolean. Defaults to `true`.
-
-### `use-pyodide`
-
-**Type:** `boolean`
-
-Whether to generate using `pyodide` instead of `python`. If there is no python installed on your device, we will default to using pyodide to generate the code.
+**This emitter has moved to [this](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-python) repo.**