On 19 May 2016 at 08:47, Avram Lubkin <aviso@xxxxxxxxxxxxxx> wrote: > I'd suggest running pylint against the packages and skipping anything below > a certain threshold. There are currently over 80,000 packages on PyPi and > the vast majority are poorly written. > That isn't why he is doing this. I don't think he is looking to get 15,000 packages added to Fedora. He is just making sure that if you need that poorly written python software... it is still in an rpm somewhere. The bigger thing he is working on is the tool to do this and probably eventually for other mega-repos.. the outcome is a side effect which may be useful to people or not.. yay if it is.. no skin off his nose if it isn't. > I think a more worthwhile effort would be to use the PyPi package rankings > (http://pypi-ranking.info/alltime) and identify any packages in say the top > 500 that don't currently have Fedora packages or aren't included in the > standard library. > > > On Thu, May 19, 2016 at 2:51 AM, Miroslav Suchy <msuchy@xxxxxxxxxx> wrote: >> >> Hi, >> I just finished packaging of 15 634 python3-* packages for Fedora. >> https://copr.fedorainfracloud.org/coprs/g/copr/PyPI3/ >> You can click on Builds and Monitoring tab. But be aware that those >> pages are HUGE (40MB) and they are loading and rendering several >> minutes. Tab "Packages" is timeouting and this will be fixed in next >> release. >> >> I am now building python2-* packages too: >> https://copr.fedorainfracloud.org/coprs/g/copr/PyPI2/ >> >> This is only for rawhide and for statistic purposes, but there will be >> more. Read on. >> >> Once the build of python2-* packages will finish, I gather the data and >> build those packages once again in other project. Packages which >> succeeded in both PyPI2 and PyPI3 projects will be build with both >> python2-* and python3-* subpackages. Everything else will be build with >> only one subpackage. >> >> Why I am doing this? >> Because I can. :) While I can imagine several obvious scenarios how this >> can help Fedora users, I anticipate there are some use cases which I can >> not imagine now, and which will surprise me for sure. >> >> Why I'm writing this? >> This projects is not yet finished. But this is first result, which can >> be used/tested/remixed. Once this rebuilds for all Fedoras and Epels >> will be finished I will announce it to Fedora users. But right now I'm >> focused on you - developers. >> These packages were automatically generated by pyp2rpm. They may work >> (or not). So you can create some (automated) tests which can test >> functionality of all those packages. You can look why your favorite >> module failed (there is still 50k packages which are failing to build >> now) and suggest improvements to pyp2rpm: >> https://github.com/fedora-python/pyp2rpm >> Or come with something else which can raise the quality of those >> packages. The future is open and waiting for your ideas. >> >> If you have any question or idea (anything missing in our API of CLI >> tools?), do not hesitate to contact me. >> >> Mirek >> -- >> devel mailing list >> devel@xxxxxxxxxxxxxxxxxxxxxxx >> http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx > > > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx > -- Stephen J Smoogen. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
