For real work you'd want an A57 based device and if you want a lot you wouldn't buy them from the electronics store with chassis
Ergo
but you just suggested pi's are great for work
Charlie_X
Yes, I know that I can get a dedicated device.
Ergo
i saw how rpi's struggle with xbmc even
nandoflorestan joined the channel
Charlie_X
You are still missing the point. The π is driving the market for these devices. Without the π you wouldn't be seeing them,
Ergo
they were on the market before pi actually ;-)
Charlie_X
XBMC runs fine on mine. NFS support is crap
Ergo
Charlie_X: with a nice skin?
Charlie_X
FFS.
Ergo
those things are basicly android tablets without the screen
Charlie_X
Why the fuck would I care about the skin? I switch my screen off when I'm not watching a film.
nouri joined the channel
Ergo
Charlie_X: i like nice looking things and improved navigation, im just saying PI is underpowered for xbmc
Charlie_X
Phones are driving ARM. π has grabbed headlines for cheap ARM hardware
Ergo
i think it often had issues with 1080p?
nouri has quit
Charlie_X
I've no problems with 1080p. But 100 MBit might be a bottleneck
Ergo
100mbit?
I think average blu-ray disc is ~20mbit stream
(I might be mistaken here)
mejymejy has quit
Charlie_X
That's the π's network. I've not measured it
Ergo
anyhoo - right now I have an ouya for
Loetkolben joined the channel
xbmc
Charlie_X
A π is just a cheap bit of kit to do whatever you want with. Nice project on using one for a robot arm in c't a couple of issues back.
Ergo
yes, that is a great purpose for pi
Charlie_X
The "chromecast" (ie. comparable harware) are continually updating the chips. The π has some silly economic stuff that takes it outside the usual market: making stuff in Wales as opposed to Guangdong.
gawel_ is now known as gawel
cooldharma06 has left the channel
gustavofonseca joined the channel
yvl has quit
mlechner joined the channel
wiggy joined the channel
junkafarian has quit
auc joined the channel
otter768 joined the channel
yvl joined the channel
inklesspen
dstufft: woo
gustavofonseca has quit
jhauser joined the channel
tiwula joined the channel
dstufft
inklesspen: it seems to work pretty ok so far, though some things (pyramid_mailer for example) still depends on the thread local mananger, but that jsut means more PRs!
inklesspen
yay
Spanktar joined the channel
dstufft
now just to get the pyramid_tm PR accepted and released so I can stop using a git checkout :D
junkafarian joined the channel
Charlie_X
re ?
blaflamme joined the channel
kiorky joined the channel
driti joined the channel
ralala joined the channel
blockninja has quit
gustavofonseca joined the channel
Spanktar has quit
mejymejy joined the channel
digitalsatori joined the channel
plamut_ has quit
mejymejy has quit
plamut_ joined the channel
TheCowboy` joined the channel
kiorky has quit
felipeduardo joined the channel
wiggy
bah - "git clean -xdf && python3 -m venv . && bin/pip install -e ." and suddenly entrypoints work again
plamut__ joined the channel
plamut_ has quit
kiorky joined the channel
rtopliffe joined the channel
whit joined the channel
Spanktar joined the channel
Charlie_X
Don't know if it's relevant but I have find . -name "*.pyc" -delete in my config
whit has quit
wiggy
damn, pyramid's view config is so much more complex than zope's publisher
interesting, that pyramid bug is not related to ABCs. With normal base classes I get the exact same error
otter768 joined the channel
otter768 has quit
dstufft
Charlie_X: PYTHONDONTWRITEBYTECODE=1 ftw
bkuberek joined the channel
postlogic
Had that been a Perl flag it would be $[=1 .
do3cc
you made this up, right?
ronnix joined the channel
postlogic
PYTHONDONTWRITEBYTECODE is real.
rodfersou has quit
markm_ has quit
rodfersou joined the channel
sirex has quit
sirex joined the channel
Charlie_X
dstufft: I know that but that's just a loaded gun
whit joined the channel
dstufft
how is it a loaded gun
Charlie_X
postlogic: we learnt yesterday that Perl 6 will let you modify the grammar of the language at runtime.
postlogic
NO. NO NO NO.
>:-|
Charlie_X
do3cc: afraid not
postlogic
Well technically you can do similar thigns with AST I guess, but it's just not right :-/
Charlie_X
dstufft: because it almost always not what you want do to. You want a command to cleanup a virtualenv when switching branches.
dstufft
Charlie_X: eh, it's almost always exactly what I want to do ;)
my virtual environments don't live in my repo root
Charlie_X
Neither do mine (I think)
digitalsatori has quit
dstufft
my commands shouldn't go modifying random things in my virtualenv to clean out pycs
Charlie_X
The problem with all environment variables is that you have to know they're there.
dstufft
it's always there for me, it's in my shell rc file :D
Justus joined the channel
Justus
hi, I'm trying to hide links based on the permissions of the target view, how can I safely check that?
Charlie_X
I'm very happy for you. Mine is in my .hgrc file
bosim has quit
bosim joined the channel
There are lots of times when I'm very glad that there are .pyc files around
But whatever works best for you.
dstufft
Charlie_X: in what situation are you glad there are .pyc files around? I can't say I've ever been happy for them to be around so I'm curious
Charlie_X
So the bytecode doesn't need recompiling all the time.
They are just implementation artefacts that I normally don't care about.
dstufft
Ok, I guess I just don't value caching the bytecode on my development machine since there's basically no noticeable speed difference to me and it means I never have to get confused about why code isn't doing the right thing and then get all like "oh whoops need to clean out my .pycs"
betabug
hmm, problems with old .pycs happens once every 5 years I would guess
dstufft
I'm not sure i've even beenw riting Python for 5 years and it's happened to me enough to get frustrated enough to find a solution
Justus
uhm, does no one know how to check permissions on routes/views? e.g. asking pyramid "can I see route 'foo'?"
Charlie_X
dstufft: there are incidences where people have been very happy that the .pycs are around. The performance will be relative to what you're doing. You're obviously very happy with your solution but I think it has pitfalls for the unwary, which is why it's not the default. But enough bikeshedding
postlogic: that is explicitly not what is required. I do not want to check a specific permission against a known request and resource, I want to know if a route leads to a resource that requires a specific permission and if yes if I have it