Re: [Distutils] Deprecating PyPI as an OpenID Provider
On 7 June 2016 at 13:33, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/07/2016 04:24 PM, Ian Cordasco wrote: >> On Tue, Jun 7, 2016 at 2:59 PM, Donald Stufft >> wrote: >>> Longer term, Python should get a centralized Sign on across all it’s >>> web properties, which could re-implement this feature for folks who >>> want it. >> >> I agree. This is should be a goal for the PSF. This would help with >> elections and a number of other things as well. I think there are a >> few solutions like FreeIPA if anyone on this list is interested in >> looking into helping the PSF implement this. > > IIRC, Christian Heimes works on FreeIPA in his day job for RedHat. He does, and improving the identity management situation is also on the PSF Infrastructure Manager's TODO list - even properly documenting all our identity silos and access management requirements will take a bit of work (as in addition to the community facing services, there are also PSF staff services and backend infrastructure to take into account). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Deprecating PyPI as an OpenID Provider
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/07/2016 04:24 PM, Ian Cordasco wrote: > On Tue, Jun 7, 2016 at 2:59 PM, Donald Stufft > wrote: >> Longer term, Python should get a centralized Sign on across all it’s >> web properties, which could re-implement this feature for folks who >> want it. > > I agree. This is should be a goal for the PSF. This would help with > elections and a number of other things as well. I think there are a > few solutions like FreeIPA if anyone on this list is interested in > looking into helping the PSF implement this. IIRC, Christian Heimes works on FreeIPA in his day job for RedHat. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJXVy+lAAoJEPKpaDSJE9HYIBcQAImzTHtAzENNR//GswKjxrCT zYxSQzdsQtBjpWOB279roeHfpZRSf6xhy9HjUhOWGIQ+nDgEcIgDUIU1BIg2ZPgJ zQcMcjV0wiOAeyeVdgRtKXw3o4UW4XijuS43C29s+rxHvGPLPziQGQLWk7SZdzjf YAi12Us96rj2m0uuXjpOPVZjrztI0ABdcA2yRJuDYiMtVONH/4TP86n6NHnUznO1 RCoPsfLTn7BbU1hMDOdrGKOED4QYNskiDAiB5qtL/uB8zDgKRLlIhxTHq9/d2T7D 0836zTvNwoo/TwBwfUFn1Op8CXydls7yGfpRq43NNqgBNwhWxzImpfVTxB+D8MHm NCd4tPvgSJdyov2loYqToCytH3d+ueKdL77PG9ag7GCuOcrTggbBLhG5aaNknOSo LN/yZgF+geuGp81WlHNwl3duo0JgapX/ilQg96IZSy19DzZa4/mihJu1SurGB53u Jj7bpz10wCBMK5NJqzFYJ/gcAEqPQ7E6jzFQps65Eqs3HQTb33xOryptpmc7kZSR fT/NJG+0ctwjdAbr7pZX0Jyg8G2hWEOsi+pfY/22Ejs4gxmNnMWqqVcLzBm7glB2 sDc4sm573WtDRM6+dkCyyjKZMYwvWSbsIlWiIo27pdHXOTx4fGKxiJgqt4cD1IhC DN02co6A9A+t5Meory24 =fMAO -END PGP SIGNATURE- ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Deprecating PyPI as an OpenID Provider
On Tue, Jun 7, 2016 at 2:59 PM, Donald Stufft wrote: > Longer term, Python should get a centralized Sign on across all it’s web > properties, which could re-implement this feature for folks who want it. I agree. This is should be a goal for the PSF. This would help with elections and a number of other things as well. I think there are a few solutions like FreeIPA if anyone on this list is interested in looking into helping the PSF implement this. Cheers, Ian ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] Deprecating PyPI as an OpenID Provider
Just a heads up, I do not intend to implement the “Use PyPI as an OpenID Provider” functionality in Warehouse. Looking at the actual usage of this, it appears that very few people have ever taken advantage of it (a total of 201 (user, site) combinations in the database of what people have set to “Allow Always”) and I don’t believe it’s worth continuing. Longer term, Python should get a centralized Sign on across all it’s web properties, which could re-implement this feature for folks who want it. If you’re using this for anything, I recommend migrating off of it onto something else. Warehouse Issue: https://github.com/pypa/warehouse/issues/60 — Donald Stufft ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] How to register my python package which relys on the output of other project on pypi
My pysdl2-cffi project has a dependency ':sys_platform=="win32"': ['sdl2_lib'] meaning 'depends on sdl2_lib only on Windows' (see its setup.py). sdl2_lib is a specially made wheel that only contains DLL's for Windows. On other platforms we don't try to install sdl2_lib, assuming you have already installed SDL2 some other way. If I wanted to distribute the Linux so's on PyPy I could upload a second wheel with the 'manylinux1' tag, and pip would choose the right one. Distributing Linux binaries is more complicated than for Windows, see PEP 513 and https://pypi.python.org/pypi/auditwheel On Tue, Jun 7, 2016 at 10:32 AM Young Yang wrote: > Hi, > > I'm writing a python-binding project for project A written in C++. > Project A is on github. It supports compiling itself to produce .so in > linux or .dll in windows. > My python-binding project contains depends on the .dll and .so file. > > Now I want to register my package on pypi. So that users can install my > package with only running `pip install `. > > I have to support both windows and linux. The only solution I can figure > out is to include both .dll and .so in my package. This will end up with > both .so and .dll installed in any platforms. It sounds dirty. > > Is there any better ways to achieve my goal? > > > PS: The compile process of Project A is a little complicated, so I can't > use python Extension to build my dynamic library. > > > This question comes after this question > https://mail.python.org/pipermail/distutils-sig/2016-June/029059.html > > Thanks in advance :) > > > -- > Best wishes, > Young Yang > ___ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
[Distutils] How to register my python package which relys on the output of other project on pypi
Hi, I'm writing a python-binding project for project A written in C++. Project A is on github. It supports compiling itself to produce .so in linux or .dll in windows. My python-binding project contains depends on the .dll and .so file. Now I want to register my package on pypi. So that users can install my package with only running `pip install `. I have to support both windows and linux. The only solution I can figure out is to include both .dll and .so in my package. This will end up with both .so and .dll installed in any platforms. It sounds dirty. Is there any better ways to achieve my goal? PS: The compile process of Project A is a little complicated, so I can't use python Extension to build my dynamic library. This question comes after this question https://mail.python.org/pipermail/distutils-sig/2016-June/029059.html Thanks in advance :) -- Best wishes, Young Yang ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
