Python Packages

Python Packages

[Allen Hewes]

Hi,

I have a few Python packages built (and very minor change) for Python 3.8, but before I follow the directions for package contributions, I have a few questions:

1. I am only running cygport --64 <PYTHON-PACKAGE>.cygport all-test, is there anything else I should do? I have a local "test" repo I use to get them installed via Cygwin Setup.

2. I am using the --64 arg to cygport because I don't have a 32-bit install of Cygwin, must I get a 32-bit Cygwin install running so I can make 32-bit packages (to be uploaded)?

3. Is there decorum for this of work for Cygwin? Like a packagers mailing list?

4. Do I or should I have a package mentor? Right now, I am "winging" it b/c my consumer is myself, but I'd like to know how the sausage is made so I Do It Right.

The Python  packages in the Python 3.8 flavor I have ready:
python38-asn1crypto
python38-crypto
python38-cryptography
python38-lockfile
python38-openssl
python38-pyasn1
python38-pyasn1-modules

Thanks,

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

Re: Python Packages

[Marco Atzeri]

On 30.07.2020 06:57, Allen Hewes via Cygwin wrote:
> Hi,
> 
> I have a few Python packages built (and very minor change) for Python 3.8, but before I follow the directions for package contributions, I have a few questions:
> 
> 1. I am only running cygport --64 <PYTHON-PACKAGE>.cygport all-test, is there anything else I should do? I have a local "test" repo I use to get them installed via Cygwin Setup.
> 
> 2. I am using the --64 arg to cygport because I don't have a 32-bit install of Cygwin, must I get a 32-bit Cygwin install running so I can make 32-bit packages (to be uploaded)?

on 64 bit the --64 is superfluos
You will need a 32 bit installation for the 32bit packages, but most are 
"noarch" so you need to build only once

> 
> 3. Is there decorum for this of work for Cygwin? Like a packagers mailing list?

cygwin-apps(at)cygwin(dot)com is for packagers

https://cygwin.com/lists.html

> 
> 4. Do I or should I have a package mentor? Right now, I am "winging" it b/c my consumer is myself, but I'd like to know how the sausage is made so I Do It Right.

post on that list and we all try to mentor you

> 
> The Python  packages in the Python 3.8 flavor I have ready:
> python38-asn1crypto
> python38-crypto
> python38-cryptography
> python38-lockfile
> python38-openssl
> python38-pyasn1
> python38-pyasn1-modules

I am currently building from one source for at least 3.6, 3.7 and 3.8
have you looked on the previous source from Yaakov or some of my
last one ?


> Thanks,
> 
> /allen
> 

RE: Python Packages

[Allen Hewes]

> > I have a few Python packages built (and very minor change) for Python 3.8,
> but before I follow the directions for package contributions, I have a few
> questions:
> >
> > 1. I am only running cygport --64 <PYTHON-PACKAGE>.cygport all-test, is
> there anything else I should do? I have a local "test" repo I use to get them
> installed via Cygwin Setup.
> >
> > 2. I am using the --64 arg to cygport because I don't have a 32-bit install of
> Cygwin, must I get a 32-bit Cygwin install running so I can make 32-bit
> packages (to be uploaded)?
>
> on 64 bit the --64 is superfluos
> You will need a 32 bit installation for the 32bit packages, but most are
> "noarch" so you need to build only once
>

I think there's a few which have C interfaces. I didn't check nor am I familiar enough with Cygwin, are no-arch dirs being used for libs? I am pretty sure DLLs were built. Can someone have multi-lib/multi-arch Pythons installed in Cygwin? I've only ever used a single arch myself.

> >
> > 3. Is there decorum for this of work for Cygwin? Like a packagers mailing
> list?
>
> cygwin-apps(at)cygwin(dot)com is for packagers
>
> https://cygwin.com/lists.html
>

Thanks. Subbed.

> >
> > 4. Do I or should I have a package mentor? Right now, I am "winging" it b/c
> my consumer is myself, but I'd like to know how the sausage is made so I Do
> It Right.
>
> post on that list and we all try to mentor you
>

Thanks.

> >
> > The Python  packages in the Python 3.8 flavor I have ready:
> > python38-asn1crypto
> > python38-crypto
> > python38-cryptography
> > python38-lockfile
> > python38-openssl
> > python38-pyasn1
> > python38-pyasn1-modules
>
> I am currently building from one source for at least 3.6, 3.7 and 3.8 have you
> looked on the previous source from Yaakov or some of my last one ?
>

I am using the repos I found here: https://cygwin.com/git-cygwin-packages/. The versions I found here are the same versions I already had installed for Python 3.7. Here's the explicit package list:
python38-asn1crypto           0.24.0-1                        OK
python38-crypto               2.6.1-2                         OK
python38-cryptography         2.6.1-1                         OK
python38-lockfile             0.12.2-2                        OK
python38-openssl              19.0.0-1                        OK
python38-pyasn1               0.4.5-1                         OK
python38-pyasn1-modules       0.2.4-1                         OK

I built what's currently in the repo (with one small minor change to a single package) b/c I noticed what's going on in python-wheel cygclass. This also leads me to ask another question: must I have both Python 3.7 and Python 3.8 installed for all/any packages?

It would seem that one must make sure python-openssl 1.2.3 build and work (test suite passes) for both Python 3.7 and Python 3.8 based on this setup. Is this always true?

Also, from my inspection of the cygport's cygclasses, the "default" is to not build Python 3.6 flavored packages, only Python 3.7 and Python 3.8. Have I got that right?

I also didn't spot any testsuite passes, but I didn't check the PyPy sources if testsuites are distributed or not.

I figured it best to get what's already in the repo build for 3.8, and then consider package updates later.

Thanks,

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

Re: Python Packages

[Marco Atzeri]

On 30.07.2020 09:25, Allen Hewes via Cygwin wrote:
>>> I have a few Python packages built (and very minor change) for Python 3.8,
>> but before I follow the directions for package contributions, I have a few
>> questions:
>>>

> 
> I think there's a few which have C interfaces. I didn't check nor am I familiar enough with Cygwin, are no-arch dirs being used for libs? I am pretty sure DLLs were built. 
> Can someone have multi-lib/multi-arch Pythons installed in Cygwin? I've only ever used a single arch myself.


if there are dlls than you need to build 32 and 64 version

otherwise if they just contains *py and *pyc they are noarch

$ cygport python-cffi.cygport list | grep dll
/usr/lib/python2.7/site-packages/_cffi_backend.dll
/usr/lib/python3.6/site-packages/_cffi_backend.cpython-36m-x86_64-cygwin.dll
/usr/lib/python3.7/site-packages/_cffi_backend.cpython-37m-x86_64-cygwin.dll
/usr/lib/python3.8/site-packages/_cffi_backend.cpython-38-x86_64-cygwin.dll



Regards
Marco

Re: Python Packages

[Marco Atzeri]

On 30.07.2020 06:57, Allen Hewes via Cygwin wrote:
> Hi,
> 
> I have a few Python packages built (and very minor change) for Python 3.8, but before I follow the directions for package contributions, I have a few questions:
> 
> 1. I am only running cygport --64 <PYTHON-PACKAGE>.cygport all-test, is there anything else I should do? I have a local "test" repo I use to get them installed via Cygwin Setup.
> 
> 2. I am using the --64 arg to cygport because I don't have a 32-bit install of Cygwin, must I get a 32-bit Cygwin install running so I can make 32-bit packages (to be uploaded)?
> 
> 3. Is there decorum for this of work for Cygwin? Like a packagers mailing list?
> 
> 4. Do I or should I have a package mentor? Right now, I am "winging" it b/c my consumer is myself, but I'd like to know how the sausage is made so I Do It Right.
> 
> The Python  packages in the Python 3.8 flavor I have ready:
> python38-asn1crypto
> python38-crypto
> python38-cryptography
> python38-lockfile
> python38-openssl
> python38-pyasn1
> python38-pyasn1-modules
> 
> Thanks,
> 
> /allen
> 

Hi Allen,
as you have not follow up on cygwin-apps, I updated them and
they should show up shortly

Regards
Marco

RE: Python Packages

[Allen Hewes]

> > 4. Do I or should I have a package mentor? Right now, I am "winging" it b/c
> my consumer is myself, but I'd like to know how the sausage is made so I Do
> It Right.
> >
> > The Python  packages in the Python 3.8 flavor I have ready:
> > python38-asn1crypto
> > python38-crypto
> > python38-cryptography
> > python38-lockfile
> > python38-openssl
> > python38-pyasn1
> > python38-pyasn1-modules
> >
> > Thanks,
> >
> > /allen
> >
>
> Hi Allen,
> as you have not follow up on cygwin-apps, I updated them and they should
> show up shortly
>
> Regards
> Marco
>

Thanks Marco. Yep, I have joined the ML but I haven't had time to get back to Cygwin-y things yet. I still have to do some tasks from the contributor section on cygwin.com.

I'll see you in the cygwin-apps ML.

Thanks,

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.