Re: [openstack-dev] Paste unmaintained
On Wed, 8 Aug 2018, Thomas Goirand wrote: I'll try to investigate then. However, the way you're suggesting mandates systemd which is probably not desirable. "or some other supervisor" -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] Paste unmaintained
On 08/08/2018 04:38 PM, Chris Dent wrote: > On Wed, 8 Aug 2018, Thomas Goirand wrote: > >> I'd be more than happy to have a better logging without the need of >> paste/pastescript, but so far, that's the only way I found that worked >> with uwsgi. Do you know any other way? > > Yes, use systemd or some other supervisor which is responsible for > catching stderr. That's why I pointed to devstack and my container > thing. Not because I think devstack is glorious or anything, but > because the logging works and presumably something can be learned > from that. > > Apparently what you're doing in the debian packages doesn't work > (without logging middleware), which isn't surprising because that's > exactly how uwsgi and WSGI is supposed to work. > > What I've been trying to suggest throughout this subthread is that > it sounds like however things are being packaged in debian is not > right, and that something needs to be changed. Also that your bold > assertion that uwsgi doesn't work without paste is only true in the > narrow way in which you are using it (which is the wrong way to use > it). Thanks. I'll try to investigate then. However, the way you're suggesting mandates systemd which is probably not desirable. Cheers, Thomas Goirand (zigo) __ 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
Re: [openstack-dev] Paste unmaintained
On Wed, 8 Aug 2018, Thomas Goirand wrote: I'd be more than happy to have a better logging without the need of paste/pastescript, but so far, that's the only way I found that worked with uwsgi. Do you know any other way? Yes, use systemd or some other supervisor which is responsible for catching stderr. That's why I pointed to devstack and my container thing. Not because I think devstack is glorious or anything, but because the logging works and presumably something can be learned from that. Apparently what you're doing in the debian packages doesn't work (without logging middleware), which isn't surprising because that's exactly how uwsgi and WSGI is supposed to work. What I've been trying to suggest throughout this subthread is that it sounds like however things are being packaged in debian is not right, and that something needs to be changed. Also that your bold assertion that uwsgi doesn't work without paste is only true in the narrow way in which you are using it (which is the wrong way to use it). -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] Paste unmaintained
On 08/08/2018 10:43 AM, Chris Dent wrote: > On Wed, 8 Aug 2018, Thomas Goirand wrote: > >> If you don't configure uwsgi to do any special logging, then then only >> thing you'll see in the log file is client requests, without any kind of >> logging from the wsgi application. To have proper logging, one needs to >> add, in the uwsgi config file: >> >> paste-logger = true >> >> If you do that, then you need the python3-pastescript installed, which >> itself depends on the python3-paste package. >> >> Really, I don't see how an operator could run without the paste-logger >> option activated. Without it, you see nothing in the logs. > > I'm pretty sure your statements here are not true. In the uwsgi > configs for services in devstack, paste-logger is not used. I have never mentioned devstack ! :) > Can you please point me to where you are seeing these problems? In the Debian packages, if I don't do paste-logger = true, I will not see any debug output. > Clearly something is confused somewhere. Is the difference in our > experiences that both of the situations I describe above are happy > with logging being on stderr and you're talking about being able to > config logging to files, within the application itself? If there's no paste-logger, what the application prints on stderr doesn't appear in the log file that uwsgi logs into. That's precisely what paste-logger fixes. > If that's > the case then my response would b: don't do that. Let systemd, or > your container, or apache2, or whatever process/service orchestration > system you have going manage that. That's what they are there for. I'd be more than happy to have a better logging without the need of paste/pastescript, but so far, that's the only way I found that worked with uwsgi. Do you know any other way? Cheers, Thomas Goirand (zigo) __ 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
Re: [openstack-dev] Paste unmaintained
On Wed, 8 Aug 2018, Thomas Goirand wrote: If you don't configure uwsgi to do any special logging, then then only thing you'll see in the log file is client requests, without any kind of logging from the wsgi application. To have proper logging, one needs to add, in the uwsgi config file: paste-logger = true If you do that, then you need the python3-pastescript installed, which itself depends on the python3-paste package. Really, I don't see how an operator could run without the paste-logger option activated. Without it, you see nothing in the logs. I'm pretty sure your statements here are not true. In the uwsgi configs for services in devstack, paste-logger is not used. In the uwsgi set up [1] I use in placedock [2], paste-logger is not used. Yet both have perfectly reasonable logs showing a variety of log levels, including request logs at INFO, and server debugging and warnings where you would expect it to be. Can you please point me to where you are seeing these problems? Clearly something is confused somewhere. Is the difference in our experiences that both of the situations I describe above are happy with logging being on stderr and you're talking about being able to config logging to files, within the application itself? If that's the case then my response would b: don't do that. Let systemd, or your container, or apache2, or whatever process/service orchestration system you have going manage that. That's what they are there for. [1] https://github.com/cdent/placedock/blob/master/shared/placement-uwsgi.ini [2] https://github.com/cdent/placedock -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] Paste unmaintained
On 08/07/2018 05:17 PM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2018-08-07 16:57:59 +0200: >> On 08/02/2018 04:27 PM, Doug Hellmann wrote: >>> >>> 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. >> >> Doug, >> >> That's nice to have direct dependency, but this doesn't cover >> everything. If using uwsgi, if you want any kind of logging from the >> wsgi application, you need to use pastescript, which itself runtimes >> depends on paste. So, anything which potentially has an API also depends >> indirectly on Paste. > > I'm not sure why that would be the case. Surely *any* middleware could > set up logging? > > Doug Doug, If you don't configure uwsgi to do any special logging, then then only thing you'll see in the log file is client requests, without any kind of logging from the wsgi application. To have proper logging, one needs to add, in the uwsgi config file: paste-logger = true If you do that, then you need the python3-pastescript installed, which itself depends on the python3-paste package. Really, I don't see how an operator could run without the paste-logger option activated. Without it, you see nothing in the logs. I hope this helps, Cheers, Thomas Goirand (zigo) __ 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
Re: [openstack-dev] Paste unmaintained
Excerpts from Thomas Goirand's message of 2018-08-07 16:57:59 +0200: > On 08/02/2018 04:27 PM, Doug Hellmann wrote: > > > > 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. > > Doug, > > That's nice to have direct dependency, but this doesn't cover > everything. If using uwsgi, if you want any kind of logging from the > wsgi application, you need to use pastescript, which itself runtimes > depends on paste. So, anything which potentially has an API also depends > indirectly on Paste. I'm not sure why that would be the case. Surely *any* middleware could set up logging? Doug __ 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
Re: [openstack-dev] Paste unmaintained
On Tue, 7 Aug 2018, Thomas Goirand wrote: That's nice to have direct dependency, but this doesn't cover everything. If using uwsgi, if you want any kind of logging from the wsgi application, you need to use pastescript, which itself runtimes depends on paste. So, anything which potentially has an API also depends indirectly on Paste. Can you point to more info on this, as it doesn't correspond with my experience of using uwsgi? In my experience uwsgi has built in support for logging without dependencies: https://uwsgi-docs.readthedocs.io/en/latest/LogFormat.html As I said in IRC a while ago: It doesn't really matter how many of our projects are using Paste or PasteDeploy: If any of them are, then we have a problem to address. We already know that some of the big/popular ones use it. That's enough to require us to work on a solution. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] Paste unmaintained
On 08/02/2018 04:27 PM, Doug Hellmann wrote: > > 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 |
Re: [openstack-dev] Paste unmaintained
On Mon, Aug 06, 2018 at 09:53:36AM -0500, Lance Bragstad wrote: > > > > > Morgan has been working through the migration since June, and it's been > quite involved [0]. At one point he mentioned trying to write-up how he > approached the migration for keystone. I understand that not every > project structures their APIs the same way, but a high-level guide might > be helpful for some if the long-term goal is to eventually move off of > paste (e.g. how we approached it, things that tripped us up, how we > prepared the code base for flask, et cetera). > > I'd be happy to help coordinate a session or retrospective at the PTG if > other groups find that helpful. > I would find this very useful. I'm not sure the Cinder team has the resources to tackle something like this immediately, but having a better understanding of what would be involved would really help scope the work. And if we have existing examples to follow and at least an outline of the steps to do the work, it might be a good low-hanging-fruit type of thing for someone to tackle if they are looking to get involved. __ 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
Re: [openstack-dev] Paste unmaintained
On Thu, Aug 2, 2018 at 4:27 PM, Doug Hellmann 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
Re: [openstack-dev] Paste unmaintained
On 08/02/2018 09:36 AM, Chris Dent wrote: > On Thu, 2 Aug 2018, Stephen Finucane wrote: > >> 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. > > I've sent some exploratory email to Ian, the original author, to get > a sense of where things are and whether there's an option for us (or > if for some reason us wasn't okay, me) to adopt it. If email doesn't > land I'll try again with other media > > I agree with the idea of trying to move away from using it, as > mentioned elsewhere in this thread and in IRC, but it's not a simple > step as at least in some projects we are using paste files as > configuration that people are allowed (and do) change. Moving away > from that is the hard part, not figuring out how to load WSGI > middleware in a modern way. ++ Keystone has been battling this specific debate for several releases. The mutable configuration goal in addition to some much needed technical debt cleanup was the final nail. Long story short, moving off of paste eases the implementations for initiatives we've had in the pipe for a long time. We started an effort to move to flask in Rocky. Morgan has been working through the migration since June, and it's been quite involved [0]. At one point he mentioned trying to write-up how he approached the migration for keystone. I understand that not every project structures their APIs the same way, but a high-level guide might be helpful for some if the long-term goal is to eventually move off of paste (e.g. how we approached it, things that tripped us up, how we prepared the code base for flask, et cetera). I'd be happy to help coordinate a session or retrospective at the PTG if other groups find that helpful. [0] https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+branch:master+topic:bug/1776504 > > > > __ > 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 signature.asc Description: OpenPGP digital signature __ 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
Re: [openstack-dev] Paste unmaintained
On Thu, 2 Aug 2018, Stephen Finucane wrote: 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. I've sent some exploratory email to Ian, the original author, to get a sense of where things are and whether there's an option for us (or if for some reason us wasn't okay, me) to adopt it. If email doesn't land I'll try again with other media I agree with the idea of trying to move away from using it, as mentioned elsewhere in this thread and in IRC, but it's not a simple step as at least in some projects we are using paste files as configuration that people are allowed (and do) change. Moving away from that is the hard part, not figuring out how to load WSGI middleware in a modern way. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent__ 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
Re: [openstack-dev] Paste unmaintained
On Thu, Aug 2, 2018 at 10:27 AM, Doug Hellmann 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
Re: [openstack-dev] Paste unmaintained
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 |
[openstack-dev] Paste unmaintained
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 __ 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
