GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Distinguish "active" from "historical" enviorments · Issue #99 · python/codespeed

Distinguish "active" from "historical" enviorments #99

New issue
Copy link
New issue
Copy link
Open
Open
Distinguish "active" from "historical" enviorments#99
Copy link

Description

@StanFromIreland
StanFromIreland
opened on Nov 1, 2026
Issue body actions

Several environments are historical, but this isn't immediately obvious. One option would be to rename them (is this safe...?), while another would be to group them in a semi-hidden tab somewhere?

Activity

  1. mattip commented on Nov 2, 2026

    @mattip
    mattip
    on Nov 2, 2026
    More actions

    They could be behind an accordion, like the executables on https://speed.pypy.org/comparison/. Then the defaults could have an DEF_ACTIVE_ENV entry.

    Reacted by Stan Ulbrych
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
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.