There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)

There are potential benefits for choosing PyPI or conda. PyPI has one global namespace and distributed ownership of that namespace. Because of this, it is easier within PyPI to have single sources for a package steps: • Define the hook(s) to be registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda requests version to stable, unbundled release (#7528) • resolve #7591 updates and improvements from namespace PR for 4.6 (#7599) • resolve #7592 compatibility shims (#7606) • user-agent context refactor (#7630)