Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Update PURLDB with all ABCTK releases

未关闭
#582 2 条评论 0 个 reaction 已指派 3 人 在 GitHub 查看

@pombredanne 已经在做这个了。

开始于 2025年3月15日。

评估

这个 Issue 还没有评估数据。

描述

Important needs design

We need an automated process to update PURLDB whenever we release a new version of any AboutCode.org package - we should start with aboutcode-toolkit. If we have each release in PURLDB then you should be able to get that data for a Product in DejaCode with the Improve Packages from PURLDB Action.
The steps seem to be:

  • Use the PURLDB API to get the current list of PURLs for aboutcode-toolkit and their data
  • Identify missing or incorrect data in the existing PURL data and correct it
  • Identify the missing PURLs and add them to PURLDB
  • Figure out how to automatically populate the PURLDB for each new release of aboutcode-toolkit

This is a pilot for a process to:

  • Clean up existing PURLDB data for all AboutCode projects
  • Automate adding PURLDB data for each new release of an AboutCode project
    The initial focus should be on AboutCode projects that are published to PyPI to keep this simple.

An open question is how to handle the different types of packages that we usually publish for aboutcode-toolkit (and most other AboutCode projects). Using v11.0.0 AboutCode Toolkit v11.0.0 as an example, we have 4 downloads:

  • aboutcode_toolkit-11.0.0-py3-none-any.whl
  • aboutcode_toolkit-11.0.0.tar.gz
  • v11.0.0.zip (Source Code)
  • v11.0.0.tar.gz (Source Code)

For patch releases like AboutCode Toolkit v11.0.1 and v11.0.2 (and many older versions) we only release the source packages.
Since each PURLDB record has one Download URL we will need some way to record the four different PURLs.
This seems to call for a qualifier so that the records will be unique. My guess is that we might want to treat the wheel as primary in the PyPI context and perhaps not use a qualifier for it.

主要语言
Python
星标
100
派生
48
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aboutcode-org/aboutcode-toolkit 的其他 Issue

查看 aboutcode-org/aboutcode-toolkit 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。