[Distutils] [Python-ideas] Version control system link in package meta data

Wes Turner wes.turner at gmail.com
Sat Apr 9 10:04:42 EDT 2016

* JSONLD / RDFa would be easier to parse, someday:
https://github.com/pypa/interoperability-peps/issues/31 #PEP426JSONLD

Warehouse had placeholders for e.g. extra metadata like source URLs.

* https://github.com/pypa/warehouse
  * https://warehouse.python.org/project/pip/

cases where we can try to 'infer' a source URL:

* 1. when specified as an extra package metadata attribute
   * how to specify (version, VCS_Rev) pairs?
     * semver 3.0.0+buildVCSREV ?
        * https://warehouse.python.org/project/semantic_version/

* 2. when homepage.domain in [github.com, bitbucket.org]

  * sphinxcontrib-srclinks has sane defaults and expansions:
    * | Warehouse:
    * | PyPI: https://pypi.python.org/pypi/sphinxcontrib-srclinks/
    * | Src:
    * | Src: git https://bitbucket.org/westurner/sphinxcontrib-srclinks

* git+ssh://git@github.com/pypa/pip@tag#egg=pip

sure would be nice to specify a Src URL as a ## comment for each
Requirement string block e.g. in requirements.txt; once:

* https://github.com/westurner/pyleset/blob/release/0.1.0/setup.py
  * class Requirement
  * class RequirementsMap
    * def generate_packages_txt
    * def generate_requirements_txt

... I would be more than happy to relicense/contribute any of this with my
name on it here
On Apr 9, 2016 4:04 AM, "Tymoteusz Jankowski" <tymoteusz.jankowski at gmail.com>

> Here's <https://github.com/pypa/pip/pull/3601> a draft of the feature.
> Any feedback is appreciated.
> On Sun, Mar 13, 2016 at 10:52 AM Tymoteusz Jankowski <
> tymoteusz.jankowski at gmail.com> wrote:
>> Thanks for information. I think that's enough to me. I'm gonna check all
>> URLs in package data and if anyone match to VCS i clone it. If not fallback
>> to regular package installation.
>> On Sat, Mar 12, 2016 at 3:46 PM Nick Coghlan <ncoghlan at gmail.com> wrote:
>>> On 12 March 2016 at 20:44, Alexander Walters <tritium-list at sdamon.com>
>>> wrote:
>>> > I agree, it would be nice if everyone used git (or any of a small set
>>> of
>>> > VCS), and all the packages on pypi listed their repositories in the
>>> > metadata.  If that were the case, this tool might already exist.  In
>>> the
>>> > current state of things, though, i don't think it makes much sense to
>>> > produce a general purpose tool for this.
>>> We don't place any particular requirements on the development
>>> practices of projects publishing their releases through PyPI, so
>>> there's no requirement for a public VCS URL to even exist for a
>>> project, let alone for it to be mentioned in the project metadata.
>>> That said, since project URLs do make it possible for projects to
>>> share that metadata if they want to, this is a situation where a
>>> "checkout-pypi-project" that gained popularity might provide more
>>> incentive for maintainers to provide that metadata and keep it up to
>>> date. As a fallback for projects without that metadata, searching
>>> popular hosting sites like GitHub, BitBucket, GitLab and even
>>> SourceForge, would provide some initial links to investigate.
>>> Cheers,
>>> Nick.
>>> --
>>> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
> _______________________________________________
> Distutils-SIG maillist  -  Distutils-SIG at python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20160409/5d55a84f/attachment.html>

More information about the Distutils-SIG mailing list