On Thu, Aug 2, 2018 at 4:27 PM, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Stephen Finucane's message of 2018-08-02 15:11:25 +0100: >> tl;dr: It seems Paste [1] may be entering unmaintained territory and we >> may need to do something about it. >> >> I was cleaning up some warning messages that nova was issuing this >> morning and noticed a few coming from Paste. I was going to draft a PR >> to fix this, but a quick browse through the Bitbucket project [2] >> suggests there has been little to no activity on that for well over a >> year. One particular open PR - "Python 3.7 support" - is particularly >> concerning, given the recent mailing list threads on the matter. >> >> Given that multiple projects are using this, we may want to think about >> reaching out to the author and seeing if there's anything we can do to >> at least keep this maintained going forward. I've talked to cdent about >> this already but if anyone else has ideas, please let me know. >> >> Stephen >> >> [1] https://pypi.org/project/Paste/ >> [2] https://bitbucket.org/ianb/paste/ >> [3] https://bitbucket.org/ianb/paste/pull-requests/41 >> > > The last I heard, a few years ago Ian moved away from Python to > JavaScript as part of his work at Mozilla. The support around > paste.deploy has been sporadic since then, and was one of the reasons > we discussed a goal of dropping paste.ini as a configuration file. > > Do we have a real sense of how many of the projects below, which > list Paste in requirements.txt, actually use it directly or rely > on it for configuration? > > Doug > > $ beagle search --ignore-case --file requirements.txt 'paste[><=! ]' > +----------------------------------------+--------------------------------------------------------+------+--------------------+ > | Repository | Filename > | Line | Text | > +----------------------------------------+--------------------------------------------------------+------+--------------------+ > | airship-armada | requirements.txt > | 8 | Paste>=2.0.3 | > | airship-deckhand | requirements.txt > | 12 | Paste # MIT | > | anchor | requirements.txt > | 9 | Paste # MIT | > | apmec | requirements.txt > | 6 | Paste>=2.0.2 # MIT | > | barbican | requirements.txt > | 22 | Paste>=2.0.2 # MIT | > | cinder | requirements.txt > | 37 | Paste>=2.0.2 # MIT | > | congress | requirements.txt > | 11 | Paste>=2.0.2 # MIT | > | designate | requirements.txt > | 25 | Paste>=2.0.2 # MIT | > | ec2-api | requirements.txt > | 20 | Paste # MIT | > | freezer-api | requirements.txt > | 8 | Paste>=2.0.2 # MIT | > | gce-api | requirements.txt > | 16 | Paste>=2.0.2 # MIT | > | glance | requirements.txt > | 31 | Paste>=2.0.2 # MIT | > | glare | requirements.txt > | 29 | Paste>=2.0.2 # MIT | > | karbor | requirements.txt > | 28 | Paste>=2.0.2 # MIT | > | kingbird | requirements.txt > | 7 | Paste>=2.0.2 # MIT | > | manila | requirements.txt > | 30 | Paste>=2.0.2 # MIT | > | meteos | requirements.txt > | 29 | Paste # MIT | > | monasca-events-api | requirements.txt > | 6 | Paste # MIT | > | monasca-log-api | requirements.txt > | 6 | Paste>=2.0.2 # MIT | > | murano | requirements.txt > | 28 | Paste>=2.0.2 # MIT | > | neutron | requirements.txt > | 6 | Paste>=2.0.2 # MIT | > | nova | requirements.txt > | 19 | Paste>=2.0.2 # MIT | > | novajoin | requirements.txt > | 6 | Paste>=2.0.2 # MIT | > | oslo.service | requirements.txt > | 17 | Paste>=2.0.2 # MIT | > | requirements | global-requirements.txt > | 187 | Paste # MIT | > | searchlight | requirements.txt > | 27 | Paste>=2.0.2 # MIT | > | tacker | requirements.txt > | 6 | Paste>=2.0.2 # MIT | > | tatu | requirements.txt > | 18 | Paste # MIT | > | tricircle | requirements.txt > | 7 | Paste>=2.0.2 # MIT | > | trio2o | requirements.txt > | 7 | Paste # MIT | > | trove | requirements.txt > | 11 | Paste>=2.0.2 # MIT | > | upstream-institute-virtual-environment | > elements/upstream-training/static/tmp/requirements.txt | 147 | Paste==2.0.3 > |
If you look for PasteDeploy you'll find quite a few more. I know at least Heat and Swift don't depend on Paste but on PasteDeploy. -- Thomas __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev