Python Packaging Policy

Python Packaging Policy

[jgart]

Hi Guixers,

What is our approach/policy to versioning Python packages?

Since we get Python packages from PyPi in addition to other sources we
are not necessarily trying to mirror PyPi.

What is our policy then for updating Python packages in our Python library collection?

Rolling release?

Bleeding edge?

LTS?

Something else?

How are we assuring that all Python libraries are working well together?

Re: Python Packaging Policy

[zimoun]

Hi,

On Wed, 07 Dec 2022 at 17:22, jgart <jgart@dismail.de> wrote:

> What is our policy then for updating Python packages in our Python
> library collection?

The policy is to not break the other packages; guix refresh -l python-<foo>.


> How are we assuring that all Python libraries are working well together?

How?  With a lot of love. :-)


Cheers,
simon

Re: Python Packaging Policy

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

On Thu, Dec 08, 2022 at 11:48:42AM +0100, zimoun wrote:
> Hi,
> 
> On Wed, 07 Dec 2022 at 17:22, jgart <jgart@dismail.de> wrote:
> 
> > What is our policy then for updating Python packages in our Python
> > library collection?
> 
> The policy is to not break the other packages; guix refresh -l python-<foo>.
> 
> 
> > How are we assuring that all Python libraries are working well together?
> 
> How?  With a lot of love. :-)

Yeah, basically. The 'sanity-check phase helps a lot though ...

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]