Hello, the docs for request.route_url() say "if no _query keyword argument is provided, the request query string will be returned in the URL." but that doesn't seem to be my experience in reality. Am I doing something wrong, or are the docs out of date?
oh, I'm using route_path() not route_url() but I assumed it would behave similarly?
stevepiercy is now known as stevepiercy_away
ricoalpha has quit
ricoalpha joined the channel
ricoalpha has quit
ricoalpha joined the channel
cguardia joined the channel
Rizy has quit
Rizy joined the channel
pdobrogost_home has quit
pdobrogost_home joined the channel
zoidfarb has quit
ricoalpha has quit
user___ joined the channel
c0le joined the channel
ddimmich joined the channel
ddimmich has quit
ddimmich joined the channel
ddimmich has quit
tiwula has quit
d9k__ has quit
Aankhen`` has quit
user___ joined the channel
Aankhen`` joined the channel
user___ has quit
uralbash joined the channel
stevepiercy_away is now known as stevepiercy
uralbash has quit
frispete_ joined the channel
frispete has quit
Loetkolben joined the channel
stevepiercy
wiggy Zart i think i got a fix, thanks for your help with hmac and encoding
raydeo yt?
i found a bug in the authorization step in the wiki2 source code on py3.5
and wondered the best way to put it up for review: fork off feature/alchemy-scaffold-update or just put the change as an isolated PR on the same branch?
Rizy has quit
and as soon as i wrote that, i figured that a separate branch would be better so as not to hold up my docs work on the original branch
irc best rubber ducky
stevepiercy is now known as stevepiercy_away
devyani7 joined the channel
uralbash joined the channel
moei has quit
moei joined the channel
munch_ joined the channel
Loetkolben has quit
user___ joined the channel
slav0nic joined the channel
c0le has quit
uralbash has quit
ronnix joined the channel
atomekk joined the channel
areski joined the channel
bosim has quit
bosim joined the channel
stevepiercy_away is now known as stevepiercy
github joined the channel
github
[pyramid] stevepiercy pushed 3 new commits to feature/alchemy-scaffold-update: https://git.io/v22va
pyramid/feature/alchemy-scaffold-update 492b800 Steve Piercy: minor grammar
pyramid/feature/alchemy-scaffold-update 79054f0 Steve Piercy: update authentication (done)...
pyramid/feature/alchemy-scaffold-update a6db36c Steve Piercy: Merge pull request #2378 from stevepiercy/feature/alchemy-scaffold-update...
github has left the channel
plamut__ joined the channel
ronnix joined the channel
plamut__ has quit
devyani7 has quit
uralbash joined the channel
Arfrever joined the channel
nicolas joined the channel
uralbash has quit
uralbash joined the channel
user_ joined the channel
nicolas has quit
ronnix joined the channel
plamut__ joined the channel
tinker joined the channel
user_ joined the channel
ddimmich joined the channel
ddimmich has quit
ddimmich joined the channel
bochecha joined the channel
ddimmich has quit
nicolas joined the channel
mr_jolly joined the channel
uralbash has quit
uralbash joined the channel
ljosberinn joined the channel
mr_jolly has quit
ljosberinn
well, so... i manage to "fix" my beautiful utf8 problem from yesterday...
apparently, in my current chaotic environment, my sys.stdout is actually an uwsgi daemon... and the file uwsgi is trying to write to was encoded as us-ascii
"file --mime uwsgi.log" results in "uwsgi.log: text/plain; charset=us-ascii"
well, at least i think this might be the problem, still not sure tho... :)
uralbash has quit
uralbash joined the channel
nicolas has quit
rnix_ is now known as rnix
hah, actually.... i tried to put "print(locale.getlocale(), locale.getpreferredencoding())" in my wsgi.py and uwsgi responded "(None, None) ANSI_X3.4-1968"
so now i set env in uwsgi.ini explicitly to LANG=en_US.utf8
however, if i do "echo $LANG" in bash i do see it is set to en_US.UTF-8
this didn't change the file encoding tho, so obvious that wasn't a problem at all
i suppose the problem could be solved with setting the same env var in wsgi.py also...
Rizy joined the channel
agitator|hpeter joined the channel
bochecha has left the channel
user_ joined the channel
stevepiercy
ljosberinn i would assume that when the file is created, that is when its encoding is set, no?
ljosberinn
yes
stevepiercy
i presume you can set/change the encoding of the file after creation, but that's a separate operation
what's the current status of the situation you are trying to resolve?
encoding is a bitch
ljosberinn
yeah i thought about the same, but somehow doesn't make sense that now suddenly i have to explicitly do it because i never struggled with it until now :)
the weird thing is that i made it work just recently, now it is still borked :)
stevepiercy
ljosberinn now, meaning that something has changed from earlier?
ljosberinn
i am trying to set LC_ALL in different levels now... in uwsgi config, in my wsgi app, etc
stevepiercy
well, if you talk it through, often just writing it out loud, you'll figure it out