Initial commit of go-protoc-gen-mypy

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/workflows/ci.yaml

@@ -0,0 +1,34 @@
+name: CI
+on:
+  push:
+    branches:
+      - main
+    tags:
+      - "*"
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os:
+          - macos-12
+          - ubuntu-22.04
+          - windows-2022
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-go@v5
+        with:
+          go-version-file: go.work
+
+      - name: run checks
+        run: go run mage check
+
+      - name: build snapshot
+        run: go run mage snapshot

.github/workflows/release.yaml

@@ -0,0 +1,23 @@
+name: "Release"
+
+on:
+  push:
+    tags:
+      - v*
+
+jobs:
+  build:
+    name: Release
+    runs-on: ubuntu-22.04
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-go@v5
+        with:
+          go-version-file: go.work
+
+      - run: go run mage release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,5 @@
+.idea
+.vscode
+build
+dist
+node_modules

.goreleaser.yaml

@@ -0,0 +1,24 @@
+builds:
+  - main: ./cmd/protoc-gen-mypy
+    id: es
+    binary: protoc-gen-mypy
+    env:
+      - CGO_ENABLED=0
+    targets:
+      - linux_amd64
+      - linux_arm64
+      - darwin_amd64
+      - darwin_arm64
+      - windows_amd64
+archives:
+  - format_overrides:
+      - goos: windows
+        format: zip
+release:
+  mode: append
+checksum:
+  name_template: 'checksums.txt'
+snapshot:
+  name_template: "{{ incpatch .Version }}-next"
+changelog:
+  skip: true

CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 wasilibs authors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -0,0 +1,48 @@
+# go-protoc-gen-mypy
+
+go-protoc-gen-mypy is a distribution of [protoc-gen-mypy][1]. 
+It does not actually reimplement any functionality of mypy-protobuf in Go, instead compiling it
+to WebAssembly, and executing with the pure Go Wasm runtime [wazero][2].
+This means that `go install` or `go run` can be used to execute it, with no need to rely on external
+package managers such as Homebrew, on any platform that Go supports.
+
+## Installation
+
+Precompiled binaries are available in the [releases](https://github.com/wasilibs/go-protoc-gen-mypy/releases).
+Alternatively, install the plugin using `go install`.
+
+```bash
+$ go install github.com/wasilibs/go-protoc-gen-mypy/cmd/protoc-gen-mypy@latest
+```
+
+As long as `$GOPATH/bin`, e.g. `~/go/bin` is on the `PATH`, you can use it with protoc as normal.
+
+```bash
+$ protoc --mypy_out=out/python -Iprotos protos/helloworld.proto
+```
+
+For [buf][3] users, to avoid installation entirely, it can be convenient to use `go run` in `buf.gen.yaml`.
+
+```yaml
+version: v1
+plugins:
+  - plugin: mypy
+    out: out/python
+    path: ["go", "run", "github.com/wasilibs/go-protoc-gen-mypy/cmd/protoc-gen-mypy@latest"]
+```
+
+This makes it possible to have full protobuf/gRPC generation with no installation of tools,
+besides Go itself, on any platform that Go supports. The above examples use `@latest`, but it is
+recommended to specify a version, in which case all of the developers on your codebase will use the
+same version of the tool with no special steps.
+
+See a full [example][5] in `go-protoc-gen-builtins`. To generate protos, enter the directory and run
+`go run github.com/bufbuild/buf/cmd/[email protected] generate`. As long as your machine has Go installed,
+you will be able to generate protos. The first time using `go run` for a command, Go automatically builds
+it making it slower, but subsequent invocations should be quite fast.
+
+[1]: https://github.com/nipunn1313/mypy-protobuf
+[2]: https://wazero.io/
+[3]: https://buf.build/
+[4]: https://github.com/wasilibs/go-protoc-gen-builtins
+[5]: https://github.com/wasilibs/go-protoc-gen-builtins/tree/main/example

cmd/protoc-gen-mypy/main.go

@@ -0,0 +1,12 @@
+package main
+
+import (
+	"os"
+
+	"github.com/wasilibs/go-protoc-gen-mypy/internal/pysite"
+	"github.com/wasilibs/go-protoc-gen-mypy/internal/runner"
+)
+
+func main() {
+	os.Exit(runner.Run("protoc-gen-mypy", os.Args[1:], pysite.Python, os.Stdin, os.Stdout, os.Stderr, "."))
+}

go.mod

@@ -0,0 +1,5 @@
+module github.com/wasilibs/go-protoc-gen-mypy
+
+go 1.21
+
+require github.com/tetratelabs/wazero v1.6.0

go.work

@@ -0,0 +1,7 @@
+go 1.21
+
+use (
+	.
+	./mage
+	./magefiles
+)

go.work.sum

@@ -0,0 +1,2 @@
+github.com/tetratelabs/wazero v1.6.0 h1:z0H1iikCdP8t+q341xqepY4EWvHEw8Es7tlqiVzlP3g=
+github.com/tetratelabs/wazero v1.6.0/go.mod h1:0U0G41+ochRKoPKCJlh0jMg1CHkyfK8kDqiirMmKY8A=