4 ms·

I need to publish it publicly to install it via pip, npm, cargo, etc. for public use.

mroche 6y ago
Pip does not need a package to be public in order to install it at all, I’ve installed plenty of packages from tarballs and directories just fine. From the docs[0] Install packages from: - PyPI (and other indexes) using requirement specifiers. - VCS project urls. - Local project directories. - Local or remote source archives. Although I’m not quite sure how you’re using “for public use” in that sentence. [0] https://pip.pypa.io/en/stable/reference/pip_install/#id19 https://pip.pypa.io/en/stable/reference/pip_install/#id19
- DangitBobby 6y ago
  I meant to say private use, not public use. But if I want to install from pip over the internet, which is my most common use case it needs to be publicly accessible, right? Which for me means GitHub, bitbucket, pypi, or some other bespoke solution just to avoid "publishing" something for my own private use. Or do I misunderstand?
  - lionyo 6y ago
    You can publish to a local instance of PyPi https://www.linode.com/docs/applications/project-management/how-to-create-a-private-python-package-repository/ https://www.linode.com/docs/applications/project-management/...
    - DangitBobby 6y ago
      I could do lots of things that would be unnecessarily burdensome for the dubious benefit of having my package unpublished. If it's acceptable to install it on a local network I can just do it directly from a normal filesystem.
  - JimDabell 6y ago
    GitHub and Bitbucket have private repositories and you can install from those using pip. There's nothing forcing you to make something public.
    - DangitBobby 6y ago
      I know about private repos. The hangup was installing from them. Last time I looked up how to have private python packages the the impression I got was "It's not possible." But now with a single Google search I see that it's very much possible (by using ssh). Not sure what changed other than two years have gone by.
sanderjd 6y ago
This is why I really liked the approach of using a github username as a namespace for rubygems, it lets you publish things but with some indication that it may just be for personal use.
- sgillen 6y ago
  I like that a lot! could work for personal python packages too.
  - DangitBobby 6y ago
    You can install directly from GitHub, bitbucket, etc. with pip, BTW. My point was that if I want to have packages for private use installable over the internet with package management tools for various languages, I have to put them on the public internet, or jump through some hoops.
    - harikb 6y ago
      Package management tools for both Rust and Go and JS do support direct github urls with minimal boilerplate. You have no reason to make something public unless you want to.
      - DangitBobby 6y ago
        Oh you can use those tools with private repos?
        BurpyDave 6y ago
        You can for sure with go
        steveklabnik 6y ago
        You can with Rust as well.
    - 6y ago
matheusmoreira 6y ago
I like this a lot. Publishing open source libraries and using them in private projects is a form of dogfooding.

Pip does not need a package to be public in order to install it at all, I’ve installed plenty of packages from tarballs and directories just fine. From the docs[0] Install packages from: - PyPI (and other indexes) using requirement specifiers. - VCS project urls. - Local project directories. - Local or remote source archives. Although I’m not quite sure how you’re using “for public use” in that sentence. [0] https://pip.pypa.io/en/stable/reference/pip_install/#id19 https://pip.pypa.io/en/stable/reference/pip_install/#id19

DangitBobby 6y ago
I meant to say private use, not public use. But if I want to install from pip over the internet, which is my most common use case it needs to be publicly accessible, right? Which for me means GitHub, bitbucket, pypi, or some other bespoke solution just to avoid "publishing" something for my own private use. Or do I misunderstand?
- lionyo 6y ago
  You can publish to a local instance of PyPi https://www.linode.com/docs/applications/project-management/how-to-create-a-private-python-package-repository/ https://www.linode.com/docs/applications/project-management/...
  - DangitBobby 6y ago
    I could do lots of things that would be unnecessarily burdensome for the dubious benefit of having my package unpublished. If it's acceptable to install it on a local network I can just do it directly from a normal filesystem.
- JimDabell 6y ago
  GitHub and Bitbucket have private repositories and you can install from those using pip. There's nothing forcing you to make something public.
  - DangitBobby 6y ago
    I know about private repos. The hangup was installing from them. Last time I looked up how to have private python packages the the impression I got was "It's not possible." But now with a single Google search I see that it's very much possible (by using ssh). Not sure what changed other than two years have gone by.

sanderjd 6y ago

This is why I really liked the approach of using a github username as a namespace for rubygems, it lets you publish things but with some indication that it may just be for personal use.

sgillen 6y ago
I like that a lot! could work for personal python packages too.
- DangitBobby 6y ago
  You can install directly from GitHub, bitbucket, etc. with pip, BTW. My point was that if I want to have packages for private use installable over the internet with package management tools for various languages, I have to put them on the public internet, or jump through some hoops.
  - harikb 6y ago
    Package management tools for both Rust and Go and JS do support direct github urls with minimal boilerplate. You have no reason to make something public unless you want to.
    - DangitBobby 6y ago
      Oh you can use those tools with private repos?
      - BurpyDave 6y ago
        You can for sure with go
        steveklabnik 6y ago
        You can with Rust as well.
  - 6y ago

matheusmoreira 6y ago

I like this a lot. Publishing open source libraries and using them in private projects is a form of dogfooding.