Skip to content

Pysocks (1.7.1) versus PySocks3.9 (2.0) (!) #161

Description

@NannoSilver

Hi Anorov,

At pypi.org there are two packages of PySocks.
https://pypi.org/project/PySocks/ (version 1.7.1)
https://pypi.org/project/PySocks3.9/ (version 2.0)

I see that as suspicious, and maybe there is a risk that PySocks3.9 may have some malware.
Can you confirm the PySocks3.9 is yours and, if yes, what is new in the package?

Activity

  1. SeaHOH commented on May 16, 2022

    @SeaHOH
    Contributor

    See the description of "Maintainers", the 2nd one was uploaded by megadose. Nothing new except setup metadata (at this time point).

  2. SeaHOH commented on May 16, 2022

    @SeaHOH
    Contributor

    And PySocks has stagnated.

  3. NannoSilver commented on May 16, 2022

    @NannoSilver
    Author

    See the description of "Maintainers", the 2nd one was uploaded by megadose. Nothing new except setup metadata (at this time point).

    Thank you for clarifying, SeaHOH!

  4. RoyRao2333 commented on Aug 22, 2023

    @RoyRao2333

    @SeaHOH

    Just curious: why did PySocks stop maintenance? I just stumbled on a problem that pip doesn't support socks5 connection and PySocks saved my day.

  5. SeaHOH commented on Aug 22, 2023

    @SeaHOH
    Contributor

    God knows all.

  6. chadsec1 commented on Jul 29, 2025

    @chadsec1

    @RoyRao2333 It is very much possible that "pysocks" is complete. However, looking at the author's Github, he appears to be inactive for well over 5 years at this point.

    What a shame, I might fork this and maintain it.

  7. NannoSilver commented on Jul 30, 2025

    @NannoSilver
    Author

    @RoyRao2333 It is very much possible that "pysocks" is complete. However, looking at the author's Github, he appears to be inactive for well over 5 years at this point.

    What a shame, I might fork this and maintain it.

    Do not blame the developer. I think he did a good job at the time, or at least tried, but nothing is forever, and libraries like this have a cycle.
    It will be nice if you fork and maintain it, until you feel that is the time to put focus on other priorities and, hopefully, somebody else will take from there.

  8. chadsec1 commented on Aug 13, 2025

    @chadsec1

    Do not blame the developer. I think he did a good job at the time, or at least tried, but nothing is forever, and libraries like this have a cycle.

    I am not blaming the developer, I am just saying what it is.

    It will be nice if you fork and maintain it, until you feel that is the time to put focus on other priorities and, hopefully, somebody else will take from there.

    When I finish the projects I have at hand, I will give it a go soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions