#pyramid

sphinxcontrib-argparser is well name. i keep muttering "arg" trying to figure this out

well, i got pdistreport to work with argparse, but i just cannot figure out how to get sphinxcontrib-autoprogram to render its help. anyone got a suggestion? https://github.com/Pylons/pyramid/pull/2842/

i just can't figure out how to get at the function's parser variable

stevepiercy: have a function that creates the parser and return it

stevepiercy: and specify it in the directive

PCreateCommand.parser

the parser is created in main() already. i tried returning parser in main(), and calling that

seems wrong

goodwill wrong file

i've moved onto pdistreport

move the parser creation into it's own function

that main class

calls

ah, ok

arg indeed

meh, sphinx still doesn't like it

so frustrating

finally

o/

\o

\o/

\m/

~o~

good morning

gooooood morning

with Traversal what's the proper way to generate an url in a template when it's not for a resource ?

mage_: if it's not for a resource, what's it for?

found it :) request.relative_url does what I want

if I have a view that should return either HTML or JSON regarding some header is it better to add the view twice with a different rendered or should I use custom_predicates?

mage_: one function with two view_configs, and you'll probably need a custom predicate to make the decision based on the header contents

thanks

hey everybody!

I am back again to ask for ideas regarding serving multiple fqdn's within the same pyramid app

views can serve different content based on request.host (or request.domain for that matter)

im doing this right now - (writing a cms)

mamalos: whats the problem?

and I found a not-so-elegant solution to serve static content by doing this: http://pastebin.com/6RKvaDyK

Ergo: Cool! (that you're writing a cms I mean:))

mamalos: static views should be handled by your apache/nginx in the end ;-)

ergo: my "solution" allows for any sort of static view handling (eg. passing different external uri's for each different fqdn)

mamalos: look at x-send-file header as one of the approaches you can take if you need to make this more dynamic

Ergo: did you read the pastebin? Because I'm using pyramid's static_view to serve my static assets, only I configure static_views member variables dynamically, based on my request

Ergo: but I was thinking if there was a "more elegant" solution than this (not that mine is not elegant, but it seems rather "hackee")

mamalos: yes - but do you expect any "serious" traffic?

Ergo: I'd certainly hope so! :)

because you block python threads to serve static assets

i would offload the work as much as i can from python application if you expect serious numbers

Ergo: you mean in order to generate the different urls that serve each request?

with x-sendfiles you can "hint" webserver on file location based on your requirements

so you can do something like

domain a.com serves from /upload/a.com, domain b.com from /upload/b.com

bur you can make it "transparent" to user - and use any url scheme you want

or make restricted static assets etc.

OK, and how does it work with x-sendfiles? upload/a.com etc are not generated via pyramid?

thats an implementation detail

so it depends on your application

I'm asking you because I'm not sure what is different -design wise- when using x-sendfiles and when using pyramid's routing

but let me first check what x-sendfile is about, because I'm asking you things that I have no clue about :)

Ah, so if I understood correctly, using sendfile the web server directly serves static files without giving control to pyramid?

mamalos: yes

its like request -> pyramid -> header -> proxy -> file -> response