tmsr - Search: flask

ossabot: Logged on 2019-12-29 18:13:10 diana_coman: re paster though tbh this attempt (coming as it does on top of the previous mess with python and its flask) left me looking again for not using either.

diana_coman: re paster though tbh this attempt (coming as it does on top of the previous mess with python and its flask) left me looking again for not using either.

mp_en_viaje: so how about instead of trying to shoehorn sql into supporting your idealism, you just "<a href=http://trilema.com/2016/poor-women/>bang python like a cheap whore</a>. use it, but ~don't expect~ it knows what to do with ifs ; give it tasks, but short and narrow, measurable and ~do not confide in it~. let it write against apache, not import its flask, let her do the dishes not invite her mother over to stay.

mp_en_viaje: before coming up due to portage it came up due to flask ; and after portage it came up due to http://logs.ossasepia.com/log/trilema/2019-12-04#1954347

ossabot: Logged on 2019-11-07 21:31:48 lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-07#1950107 << which relates to this; the above patched bot is still python-powered. (Granted, the flask bits have been removed, along with dependencies on things like the "Requests" library, etc.)

lobbes: http://logs.ericbenevides.com/log/trilema/2019-11-07#1950107 << which relates to this; the above patched bot is still python-powered. (Granted, the flask bits have been removed, along with dependencies on things like the "Requests" library, etc.)

mircea_popescu fully expects the attempt will discover pile of debris muchly similar to http://ossasepia.com/2019/09/02/ossabot-and-its-flask-of-python-27-on-centos-6/ (and not necessarily any happy ending). but -- at least it'd be in writing.

mircea_popescu: http://logs.nosuchlabs.com/log/trilema/2019-09-06#1934316 << if this were true he'd have been using mod_python instead of flask.

mircea_popescu: (ftr, this being a purely apache job, i do expect to see flask and crap taken out ; but othrweise no problem having actual channel sitting bot in python, doesn't hafta be rewritten or anything like that.)

asciilifeform: in all seriousness, the tower o'shit for bot.py is only slightly shorter than for reader.py ( yea no 'flask' -- but dozen other similars )

snsabot: Logged on 2019-08-29 22:51:04 lobbes: For clarity, on testbed I got the eater.py and the reader.py working fine. Was able to view loglines and search with no issue (on localhost only, didn't test port forwarding). Did *not* test the bot.py, however. For reference, my version info: Flask 0.12.2; psycopg2 2.7.4; Python 2.7.15

diana_coman: hm, in better & unexpected news, a fresh last-ditch try seems to possibly work - with precisely flask as lobbes's (http://logs.nosuchlabs.com/log/trilema/2019-08-29#1932146)

snsabot: Logged on 2019-08-29 18:38:11 asciilifeform: ( mp is fond of old php , but it suffers from 100% of same headaches , and in fact even slower , esp. if the job is even slightly moar complicated than wp ; he arrived at it same way i did at 'flask' -- picked up decade ago and 'it worx, i'ma pour cement on this' )

snsabot: Logged on 2019-08-29 18:27:23 diana_coman: to cite from flask's description, for full allergy-triggers: A micro-framework for Python based on Werkzeug, Jinja 2 and good intentions

diana_coman: re logger atm I am undecided as my options so far seem to be: 1. do another round of madness with flask until it works on this old (but stable at least) centos 2. replicate environment aka burn down centos and have fun installing remotely on the machine cuntoo 3. simply run irssi (as I'm otherwise running this code anyway as my client) with logging to db into an mp-wp database and be done with it (possibly each line a one comment - will end

spyked: tuff, which I suspect would make the result no different than either flask or hunchentoot

lobbes: For clarity, on testbed I got the eater.py and the reader.py working fine. Was able to view loglines and search with no issue (on localhost only, didn't test port forwarding). Did *not* test the bot.py, however. For reference, my version info: Flask 0.12.2; psycopg2 2.7.4; Python 2.7.15

asciilifeform: diana_coman: on testbed , print flask.__version__ >> 0.10.1 ; python --version >> 2.7.5 ;

diana_coman: the full list of stuff pulled in by flask seems to be: flask Werkzeug itsdangerous Jinja2 MarkupSafe

diana_coman: I have python 2.7.16 flask 1.1.1 and werkzeug 0.15.5 from what I see and the reader.py fails complaining that there is no flask.ext.cache , which seems to be again some version-shenanigans

diana_coman: asciilifeform: mind giving the exact versions for flask, werkzeug and whatever other shit is used in there?

asciilifeform: ( mp is fond of old php , but it suffers from 100% of same headaches , and in fact even slower , esp. if the job is even slightly moar complicated than wp ; he arrived at it same way i did at 'flask' -- picked up decade ago and 'it worx, i'ma pour cement on this' )

diana_coman: myeah, I quietly barfed in my notes re flask before but this time it just spilled in here.

snsabot: Logged on 2019-08-14 02:58:26 mp_en_viaje: Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. It began as a simple wrapper around Werkzeug and Jinja and has become one of the most popular Python web application frameworks." << really makes me want to be sober, reading that thing.

asciilifeform: diana_coman: 'flask' , 'psycopg', etc. are erry bit as rubbish as the docs suggest. with the twist that the assemblage actually worx ( phuctor's been running, incl. under various abuses , for yrs , on same ) .

diana_coman: to cite from flask's description, for full allergy-triggers: A micro-framework for Python based on Werkzeug, Jinja 2 and good intentions

diana_coman: for clarity re python 2.6 it's quite clear that it's not worth it - all sorts of breakings in flask & co really.

diana_coman: ah, yes, I'm sure 2.6ism would break 2.7, it's more this "fun" of code reuse; and I can ofc install python 2.7 on top; I seriously wonder though what's really the fastest route; because also, above it doesn't even seem to be print, it barfs when importing flask, a few layers deep in werkzeug and whatever

asciilifeform: diana_coman: 'flask' is the http shitting lib. i've used same 1 since 2013 (phuctor)

diana_coman: that flask thing gives me the hives

snsabot: Logged on 2019-08-19 16:52:17 asciilifeform: this experiment also reveals that asciilifeform's logotron will in fact stand up, with no modifications, on a python, flask, pg, etc. plucked out of arbitrary rubbish bin.

asciilifeform: this experiment also reveals that asciilifeform's logotron will in fact stand up, with no modifications, on a python, flask, pg, etc. plucked out of arbitrary rubbish bin.

asciilifeform: diana_alt: reasons to suspect the pipe, include this: i have stood up temporarily a raw flask on port 33. try time curl "http://logs.nosuchlabs.com:33/log" > /dev/null

snsabot: Logged on 2019-08-16 08:00:13 mp_en_viaje: the only possible conclusion is that unicode support is actually broken on either the flask, the python outright, or some other library asciilifeform is using there. it's true that it was coincidentally discovered by cp1252 translation failure, but it is not limited to that. things missing from nsa log like the micron above are plain unicode and correctly quoted as such by my terminal.

mp_en_viaje: the only possible conclusion is that unicode support is actually broken on either the flask, the python outright, or some other library asciilifeform is using there. it's true that it was coincidentally discovered by cp1252 translation failure, but it is not limited to that. things missing from nsa log like the micron above are plain unicode and correctly quoted as such by my terminal.

phf: also znc is incidental, i have a trivial flask (or maybe "bottle") server that parses znc logs and gives the result out in the log-format

mp_en_viaje: yes, you can use "flask" instead of apache. it's shitty, they know is shitty, the reason they "dont recommend" you put it naked on #80 is precisely that they know it's shit.

mp_en_viaje: Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. It began as a simple wrapper around Werkzeug and Jinja and has become one of the most popular Python web application frameworks." << really makes me want to be sober, reading that thing.

diana_coman: asciilifeform: it turns out I don't even usually have flask and psycopg2 on my machines

asciilifeform: fwiw i also never was able to get 'squid' to work, and phuctor is cached on 'flask' end (caches expire in 5min, moar than enuff for when some bozo links one on reddit etc)

asciilifeform: theoretically this is Right Thing, mp_en_viaje . only headache is that 'flask' etc shitshow doesn't offer any path to it.

asciilifeform: these caches live in ram ( 'flask' dun offer a disk cache, and it'd nuke the ssd at any rate )

asciilifeform: diana_coman: 'flask' is the py people's equiv. of 'hunchentoot'. eats the @app.route('/log/<chan>/<date>') etc sugars , does the 'html madlibs' thing on the 'templates' (a la 'cl-who') etc

diana_coman had no idea what flask was and barely got an idea after looking it up when it popped up in stan's logger

diana_coman: lmao; I puzzled when first saw there "flask" - but then again, not sure one can bake www-anything quickly without importing any mess

asciilifeform: mircea_popescu: re upstack , and yer gonna 'luvv' this -- i have the date link thing on operating table right nao, and loox like bug in... 'flask'

asciilifeform: the i/o device consisted of, what, 40 buttons and a 7-digit vacuum flask display.

mircea_popescu: http://btcbase.org/log/2018-02-07#1782359 << hey, my car has a flask of rum in the net behind the front seat. and i drink it, too. ☝︎

douchebag: Well, the web application would just be for viewing purposes, the PGP operations will still be done via command line. I am quite comfortable writing web apps using Python's Flask web framework

a111: Logged on 2017-05-30 18:11 asciilifeform: ( everyone who has cultured something -- knows this. exhausted culture soup goes into vacuum flask, which gotta be killed before you can empty into waste drum, and often this proves harder than expected )

asciilifeform: ( everyone who has cultured something -- knows this. exhausted culture soup goes into vacuum flask, which gotta be killed before you can empty into waste drum, and often this proves harder than expected ) ☟︎

mircea_popescu: what the fuck is so hard about making a surgical steel flask rather than obscure zamaks

Framedragger: btw, i once screwed around with memoization in flask. iirc something can be done here as well, asciilifeform (it may be as trivial as adding a decorator before the function which handles GET request)

Framedragger: asciilifeform: have you profiled an http request to a permalinkable phuctor page? where's the bottleneck? curious if you could insert a thing into flask which crawls through everything and stores locally.

Framedragger: asciilifeform: and the permalink pages identifiable via fingerprint, are they generated by the flask backend, too?

PeterL: http://btcbase.org/log/2016-08-18#1524494 << If you want something standard, like a round bottom flask or a condenser, then yes it is much cheaper to get mass produced stuff. But sometimes you want something unique, like a round bottom flask with a condenser coming off at a particular angle and connected by a frit to another chamber and a couple gass line nipples, then it is much cheaper to build yourself ☝︎

PeterL: yeah, in college I compromised a couple vacuum manifolds by forgetting to add a stirbar to the flask before opening to the vacuum line

phf: flask is not standalone though, it's a wsgi service, which in turn is a python standard for doing "web application". there are competing servers for wsgi, uwsgi being most popular. i actually had to patch it for my work production, and it's not a fits in head by any means

mircea_popescu: anyway, the other point being that there's no requirement for any actual heavy lifting work be done - take flask, read through it once, snip idiocies, put it in v and voila, official tmsr boost.

mike_c: hm - actually, hasn't been touched since '13: https://github.com/pallets/flask/releases

asciilifeform: incidentally i'd actually rather have a plastic flask than one of faux pyrex

asciilifeform: my grandfather had a tv (one of the early ru tv sets) that came with a gigantic flask you would fill with water and affix to the screen

asciilifeform: potentially, one could create a sequential circuit of arbitrary complexity using laser-cut metallic baffles in a long glass vacuum flask.

asciilifeform: while we're doing peculiar miners, one might also consider another lost technology, the 'integrated'... vacuum flask.

Pierre_Rochard: doing the conversion to sum up debits and credits, can’t wait to release :). It’s written in python with flask + sqlalchemy

asciilifeform: mircea_popescu: this is more like exhortation, to downed pilot in desert, 'throw out that stale water in your flask'

bitstein: mircea_popescu: I've just been playing with gpg authentication in flask, and I'm trying to better understand how the WoT (in its current implementation) mitigates various risks.

asciilifeform: and the remaining filling in the flask, hasn't gone anywhere, but has to be removed somehow.