Some packages are no longer installable after test command is removed

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Judoscale - Save 47% on cloud hosting with autoscaling that just works
Judoscale integrates with Django, FastAPI, Celery, and RQ to make autoscaling easy and reliable. Save big, and say goodbye to request timeouts and backed-up task queues.
judoscale.com
featured
InfluxDB high-performance time series database
Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
influxdata.com
featured
  1. setuptools

    Official project repository for the Setuptools build system

    It has been printing warnings about the deprecation for close to 5 years. I don't think a few more years of support would make much of a difference.

    > WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.

    https://github.com/pypa/setuptools/commit/cd84510713ada48bf3...

  2. Judoscale

    Save 47% on cloud hosting with autoscaling that just works. Judoscale integrates with Django, FastAPI, Celery, and RQ to make autoscaling easy and reliable. Save big, and say goodbye to request timeouts and backed-up task queues.

    Judoscale logo
  3. setuptools-demo

  4. python-sdk-core

    The python-sdk-core repository contains core functionality required by Python code generated by the IBM OpenAPI SDK Generator.

    As I understand it, the warning was only generated on "python setup.py test", and not on "from setuptools.command import test", which was the deleted module.

    If you never used 'setup.py test' then the warning was never generated.

    Pulling up the first repo example I saw in the issue, https://github.com/IBM/python-sdk-core/commits/main/setup.py back in 2019 was created using

       from setuptools.command.test import test as TestCommand

  5. next-auth

    Authentication for the Web.

    from time to time config is just not willing to sit there in a list. it needs to be computed.

    just an example from a few days ago. someone needs to pull data from some remote service (maybe Vault), or generation of keys/entropy/etc. [0][1]

    of course this just means folks should wrap the whole thing in a program. but that's getting inefficient fast if every layer only accepts "env vars" or a plain JSON file.

    [0] https://github.com/nextauthjs/next-auth/pull/9638#issuecomme...

    [1] https://github.com/nextauthjs/next-auth/pull/9638#issuecomme...

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Attacks via a New OAuth flow, Authorization Code Injection, and Whether HttpOnly, PKCE, and BFF Can Help

    2 projects | dev.to | 12 Apr 2025
  • Next.js and Next-Auth V5: Guide to Social Logins(OAuth)

    3 projects | dev.to | 23 Jan 2025
  • Implementing Authentication with Clerk in Next.js

    1 project | dev.to | 14 Oct 2024
  • GET, POST, PUT & DELETE with Next.js App Router

    2 projects | dev.to | 31 Aug 2024
  • Enterprise-Level Authentication in a Containerized Environment for NextJS 13

    2 projects | dev.to | 16 Jun 2024