hey hey, I'm processing something that has limited grace time by the requestor so I need to just tell it leave the request with me and return ok while I go and handle it for however long it takes. I found pyramid-scheduler it looks more attactive than RQ which has dependency for redis
can anyone please recommend a lib to use for scheduling?
or what is defacto lib for scheduling used in pyramid world?
davisagli has quit
Belxjander has quit
Belxjander joined the channel
davisagli joined the channel
Belxjander has quit
davisagli has quit
Belxjander joined the channel
Belxjander has quit
Belxjander joined the channel
danny__ joined the channel
stevepie_
tomas have you looked at the list on trypyramid.com?
you can filter by "Task Queueing", assuming that is what you mean by "scheduling"
tomas
stevepie_: I haven't but thanks
will do
Belxjander has quit
Belxjander joined the channel
Belxjander has quit
stevepie_: both pyramid_celery
and pyramid_rq
require extra bits
Belxjander joined the channel
Belxjander has quit
Belxjander joined the channel
Belxjander has quit
Belxjander joined the channel
stevepie_
tomas maybe someone else knows. i don't do that kind of stuff yet
tomas
nps stevepie_ thanks for your help (;
danny__ has quit
danny__ joined the channel
danny__ has quit
larence has quit
Belxjander has quit
Belxjander joined the channel
x58
tomas: You can look at using async stuff that would allow you to keep things running in the background and return early, however more generally you'll want something that allows you to queue the work to be done and fetch results at a later time.
tomas: Celery and RQ are both good targets for things like that.
That'll run them as threads within your existing processes.
I'm generally not a big fan, since it ties the lifetime of your queue/workers to the lifetime of your HTTP server, but it'll work.
tomas
thanks x58 I'll keep that in mind
stevepiercy has quit
agitator joined the channel
Belxjander has quit
stevepiercy joined the channel
Belxjander joined the channel
stevepie_ joined the channel
stevepiercy has quit
agitator joined the channel
cyp joined the channel
Belxjander has quit
Belxjander joined the channel
agitator_ joined the channel
slav0nic joined the channel
atomekk joined the channel
atomekk joined the channel
areski joined the channel
Belxjander has quit
econoraptorman has quit
Belxjander joined the channel
areski joined the channel
Belxjander has quit
Belxjander joined the channel
areski joined the channel
teix joined the channel
frispete joined the channel
frispete_ has quit
hvelarde joined the channel
Antibody has quit
bochecha joined the channel
Belxjander has quit
Belxjander joined the channel
zepolen has quit
waveform joined the channel
zepolen joined the channel
zepolen has quit
Belxjander has quit
zepolen joined the channel
Belxjander joined the channel
mengu joined the channel
zepolen has quit
castaway joined the channel
zepolen joined the channel
zepolen has quit
danny__ joined the channel
hvelarde is now known as hvelarde|lunch
areski has quit
zepolen joined the channel
zepolen has quit
davisagli joined the channel
mengu has quit
erasmas joined the channel
slav0nic joined the channel
hvelarde|lunch is now known as hvelarde|away
rajesh joined the channel
Belxjander has quit
Belxjander joined the channel
bochecha has quit
bochecha joined the channel
zepolen joined the channel
zepolen has quit
zepolen joined the channel
zepolen has quit
zepolen joined the channel
egis joined the channel
npilon joined the channel
zepolen has quit
pitchum joined the channel
rajesh
hi, new to pyramid here. setup a project using the sqlalchemy cookiecutter. i'd like to make the default permission for the entire application to be DENY_ALL. so i passed a default_permission=DENY_ALL to the configurator but get this in return when i run pserve - TypeError: unhashable type: 'AllPermissionsList'. what do i need to do before setting that?
raydeo
rajesh: deny_all is not actually a permission, it's an access control entry (a 3-tuple) shorthand for (Deny, Everyone, ALL_PERMISSIONS)
what you actually should do is just define a config.set_default_permission('deny') ... some dummy permission that you'll never assign to a user
or one that you would, it doesn't really matter
if the user doesn't have that permission then they will be denied
betabug
the manual says: " permission should be a permission string to be used as the default permission"
so if DENY_ALL isn't a string, that won't work
and raydeo said what you need to do instead :-)
agitator joined the channel
rajesh
raydeo: betabug : thanks. i assumed DENY_ALL, being a 'special' ACE, was going to be applied across.
betabug
rajesh: the docs are really good, careful reading is always recommended
rajesh
betabug: yes, i should have continued reading instead of assuming. :)
brokencycle joined the channel
betabug
:-)
the first summer I worked with pyramid, I took a pdf of the documentation along, and worked most of the summer offline, only with that... it worked exceptionally well
rajesh
that approach has worked well for me before too. particularly the 'offline' part.