Re: [pylons-discuss] [off-topic] The Case Against Python 3

I can literally +1 *all* of the previous replies. Sent from a phone, please excuse the brevity. > On 24 Nov 2016, at 15:08, John Anderson wrote: > > For the last 2 years every project I've worked on has been Python3 only. At > SurveyMonkey we had ~60 different services and

Re: [pylons-discuss] what is the ideal way to connect to postgresql using alchemy scaffold

> On 14 Dec 2015, at 04:40, kk wrote: > > Hello all, > I am going to use Postgresql in my Pyramid REST ap[app. > I wish to know what is the most ideal way of securing my database? there is nothing pyramid specific in securing your database connection. > What I wish to know

Re: [pylons-discuss] pyramid or repoze.who for auth auth middleware?

FWIW in a current project we’ve abandoned the initial oauth based approach for a home-grown SSO solution based on JWT and eight lines of pyramid glue code. as author of the various consumers of this construct i’m very happy about how straightforward this all turned out to be and will definitely

Re: [pylons-discuss] Re: what's replaced colander/deform/etc

FTR same here. although for a next project i will give wichert’s toolkit a spin. it looks cleaner and with less moving parts. cornice sometimes seems to get a bit in the way. but otherwise we’re happy with it, too. hth, tom On 14 Jun 2015, at 20:50, Vincent Catalano

Re: [pylons-discuss] manage.py equivalent?

i heartily second that suggestion. click is a joy to work with! On 01 Jun 2015, at 14:00, Oliver dief...@gmail.com wrote: If you want a really easy framework for managing script options and so on, I recommend http://click.pocoo.org On 01.06.2015 12:08, Chris Withers wrote: On 01/06/2015

Re: [pylons-discuss] Webtest NoSectionError

i’m not sure why or how you would want to run your tests using “python tests.py”. i can suggest a) using pytest and b) taking a peek at our own setup here: https://github.com/pyfidelity/rest-seed https://github.com/pyfidelity/rest-seed and in particular:

Re: [pylons-discuss] Re: Connection issue with redis_session

FWIW we've been using 'regular' cookies with content encrypted by http://pythonhosted.org/itsdangerous/ for many projects now. Works like a charm. Sent from a phone, please excuse the brevity. On 16.05.2015, at 01:58, Jonathan Vanasco jonat...@findmeon.com wrote: Sorry a bit confused

Re: [pylons-discuss] Re: trypyramid.com and python 2.x

Great explanation! We should include it on the site... Sent from a phone, please excuse the brevity. On 10.05.2015, at 02:45, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/2015 08:02 PM, Mike Orr wrote: I don't know what by artisans is

Re: [pylons-discuss] WebTest functional testing

have you looked into pytest’s parametrize feature? sounds like it could apply to your case… http://pytest.org/latest/parametrize.html http://pytest.org/latest/parametrize.html hth, tom On 11 Feb 2015, at 21:12, Robert Daniels robertdaniels2...@gmail.com wrote: I am testing some code

Re: [pylons-discuss] Dynamically-generated PDF to download

Fyi I've had good experiences using phantomjs Sent from a phone, please excuse the brevity. On 25.01.2015, at 18:17, Wichert Akkerman wich...@wiggy.net wrote: On 25 Jan 2015, at 14:40, Adam Morris adam.mor...@igbis.edu.my wrote: Okay, I get that bit now, and coded it up, but when I go

Re: [pylons-discuss] Verifying user password

just as a general guide line i would always try to implement as much as possible via roles and permissions. in this case i would suggest a role of perhaps Authenticated, Verified and Anyonmous and then assign permissions to the views as your business logic seems fit. this reduces the problem

Re: stable and security upgrade

Basically there are two popular approaches: either pip + requirements.txt or buildout + versions.cfg. Googling those should give you a good starting point :-) Sent from a phone, please excuse the brevity. On 05.08.2013, at 16:11, wilk w...@flibuste.net wrote: Hi, I'm testing pyramid with

Re: Storing settings on module level -- bad idea?

Amen, brother! Sent from a phone, please excuse the brevity. On 01.02.2012, at 09:03, Rob Miller r...@kalistra.com wrote: These are reasonable points to make. But Pyramid is explicitly not trying to be the same thing that either Django or Rails is trying to be. Those are what we call

Re: Storing settings on module level -- bad idea?

On 31.01.2012, at 05:48, Chris McDonough wrote: I think it might be significantly better to just create a settings.py module in your app and put stuff in there instead of in your config file hm, i don't want to *maintain* the settings in python code, just have easy access. or else i end up

Re: Storing settings on module level -- bad idea?

, tom regards robert On Tue, Jan 31, 2012 at 12:30 PM, Tom Lazar t...@pyfidelity.com wrote: On 31.01.2012, at 05:48, Chris McDonough wrote: I think it might be significantly better to just create a settings.py module in your app and put stuff in there instead of in your config file hm, i

Re: Storing settings on module level -- bad idea?

On Jan 31, 2012, at 2:59 PM, Chris McDonough wrote: If you did what that thing suggested you'd likely write a small wrapper to run your app instead of using paster serve, so there'd be no twice. Or at least you can arrange to do that with enough imagination. true. I personally find that

Re: Storing settings on module level -- bad idea?

On Jan 31, 2012, at 3:27 PM, Malthe Borch wrote: Another option – in terms of the right thing – is to derive an object that carries just to things you need from the request, e.g. locale and logged in user, so that you don't pass around an HTTP request everywhere (and hence need to stub it out

Storing settings on module level -- bad idea?

hi there, i was getting tired of either a) having to pass in the request all over the place (mainly from views down to helper methods) in order for the latter to have access to the settings via request.settings or b) having to call get_current_registry() all the time (which would mean my tests