#pylons

hi guys. I'm having an internal discussion about django vs pyramid for a new project we're having. is there a list of companies/websites known to be using pyramid today?

jbwiv: well, my company, Mozilla, uses it

not 'my' personal company of course. ;)

benbangert: cool. does mozilla happen to have a write-up on how it's used within the company? just hoping

well, I can refer you to the projects using it

benbangert: awesome, thanks. did you have django experience before you worked with pyramids? what about solid python experience?

I haven't made any django projects no, just lots of python experience

benbangert: k, thanks. we have varying levels of python experience, so trying to make a call on the framework which would be easiest for a mix of folks

ah, I would generally choose based on what kind of website I'm building

there's some types of things that are easier/better to build with pyramid, and some with django

benbangert: that's difficult without a doc which describes which to use for each ;-)

but generally, a financial app website with portfolio and personal finance

does the database already exist? or is it a completely fresh project?

benbangert: completely fresh

I'd say try them both, if you have a team of 4, have 2 each try a small part in each framework

unfortunately that type of test will likely bias towards django, because django does a bit more hand-holding for new users up front than pyramid

django is very specific about how your project is to be laid out and organized, while pyramid is more like a library

benbangert: yeah, that's one thing we've really looked at. 40 folks in this room versus 593 in #django ;) Wondering if we'll find it an easier go with django in the short term

just given the community

although I've done a lot of RoR, and #rubyonrails having that many numbers was actually a drawback

well, this isn't the main room

the main room is #pyramid

ah

benbangert: aside from django v pyramid, we'd really like to use python3, and django supports it. however, we're also concerned that pypy support for v3 doesn't seem to be stable, and based on discussions I've seen the pypy guys aren't really motivated to make it so

i know it's premature optimization, but I have a feeling having pypy speeds available could potentially help our costs in the future

benbangert: are you guys using 2.x or 3.x?

depending on what you're doing, it could make quite a difference, yes

the new pypi is being built on pyramid, http://whoisnicoleharris.com/2015/12/31/designi...

benbangert: interesting. thanks. i'll read that

benbangert: trying to deduce from kinto and cornice if you guys use python 2.x or python 3.x but haven't found it yet. can you share? :)

I'm not actually sure what they've deployed with

we use python 2.x, 3.x and pypy

i see. it's a shame there's not an easy way to write python3 code and then refactor easily if you need to fall back to python 2 when you hit scaling issues and need pypy

benbangert: thanks for your time. I appreciate it ;)

np