Re: Python module download URIs: LFS uses pypi.org; BLFS uses pythonhosted.org?

On 1/17/25 10:59 PM, lfs ([email protected] via blfs-dev Mailing List) wrote:
> More out of interest that anything else, I was wondering why the
> Python module download location URIs, within the LFS and BLFS Books
> were not the same?
> 
> LFS examples
> 
>   Download: https://pypi.org/packages/source/f/flit-core/flit_core-3.9.0.tar.gz
>   Download: https://pypi.org/packages/source/J/Jinja2/jinja2-3.1.4.tar.gz
>   Download: https://pypi.org/packages/source/M/MarkupSafe/MarkupSafe-2.1.5.tar.gz
>   Download: https://pypi.org/packages/source/s/setuptools/setuptools-72.2.0.tar.gz
>   Download: https://pypi.org/packages/source/w/wheel/wheel-0.44.0.tar.gz
> 
> BLFS examples
> 
>   Download (HTTP): https://files.pythonhosted.org/packages/source/a/asciidoc/asciidoc-10.2.1.tar.gz
>   Download (HTTP): https://files.pythonhosted.org/packages/source/c/cssselect/cssselect-1.2.0.tar.gz
>   Download (HTTP): https://files.pythonhosted.org/packages/source/M/Mako/Mako-1.3.5.tar.gz
> 
> I do note that in the LFS Python module sections, there is an extra tag
> for each module's home page (info not in the BLFS Python module sections)
> which is listed as the pypi.org site, for example:
> 
>   Home page: https://pypi.org/project/wheel/
> 
> so why the "switch", to using pythonhosted.org, in the BLFS Book?
> 
> Alternatively, given that if one "clicks through" from the package
> home pages at pypi.org, the links to the source files link to
> pythonhosted.org, why isn't pythonhosted.org used in the LFS Book?

Because the packages were put into the books at different times.  As long as the URLs 
work, there is no reason to change them.

   -- Bruce

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page