The next SF Python Hack Night has been announced: http://www.meetup.com/sfpython/events/171271902/
Hope to see y'all there! --steve On Thursday, March 13, 2014 12:13:46 AM UTC-7, Steve Piercy wrote: > > It was announced tonight that the next SF Python Hack Night > would take place next Wednesday, March 19, at Uber. I heard > they just moved into the old Yelp HQ on Mission at Third Street, > in the same building as the Men's Wearhouse. They have not yet > posted details to the website, but it should go up in the next > day or two. If you join the group, you will be notified. > http://www.meetup.com/sfpython/ > > --steve > > > On 3/12/14 at 9:47 PM, [email protected] (Randall Leeds) > pronounced: > > >Link to next week's hack night anywhere? > >I'd totally love to work on something. > > > > > >On Wed, Mar 12, 2014 at 5:53 PM, Steve Piercy > ><[email protected]>wrote: > > > > >>Randall, > >> > >>Please look for me at tonight's SF Python presentation meet up at Yelp. > >>I'll also be at next Wednesday's hack night for Pyramid in PyCharm. I'd > >>like to see what you're doing. > >> > >>--steve > >>On Mar 12, 2014 1:45 PM, "Randall Leeds" <[email protected]> > wrote: > >> > >>> I feel like this is a great topic for a tutorial. > >>> > >>> Next Python meetup project night here in San Francisco I might start a > >>> little scaffolding project to demonstrate some of this stuff. > >>> > >>> Jonathan, if you have links to any code that'd be useful, could you > drop > >>> some here? > >>> > >>> > >>> On Wed, Mar 12, 2014 at 1:41 PM, Jonathan Vanasco < > [email protected]>wrote: > >>> > >>>> After struggling with a decision for a while, I ended up just using > >>>> fabric and building this into our deployment routine. > >>>> > >>>> Our pyramid app toggles different includes between Production and > >>>> Testing (based on environment.ini variables): > >>>> > >>>> - production > >>>> * uses compressed / minified / joined / filtered assets in /-dist > >>>> * appends a release number as the query string to all assets ( to > >>>> bust cache across releases ) > >>>> > >>>> - development > >>>> * uses normal assets in /js /css > >>>> * appends the datetime as the query string to all assets ( to bust > >>>> cache across requests ) > >>>> > >>>> before joining and minifying the js files, they're heavily > >>>> regexed/filtered. a javascript flag is set to production, logger > lines are > >>>> commented out, and lots of other changes. sometimes libraries are > patched. > >>>> > >>>> I also manage versioned assets like this: > >>>> > >>>> /js > >>>> |-- /jquery > >>>> |-- /active ( symlink to other folder in this directory ) > >>>> |-- /v1.8.1 > >>>> |-- /v1.8.5 > >>>> > >>>> the fabric deployment file is written to deploy off the /active > symlink > >>>> in each folder. It occasionally needs to be rewritten/updated , as > 3rd > >>>> party libraries sometimes will change their file structure. > >>>> > >>>> a lot of the work just re-implements the html5boilerplate build tools > ( > >>>> originally in ant, now in node ). html5boilerplate is installed into > the > >>>> virtualenv/source, and kept relatively up-to-date. instead of > running > >>>> their commands natively, I use fabric as the exclusive interface. > that > >>>> lets me move files around or do all the other work in Python. > >>>> > >>>> It took about three hours to set up and has been really great. > Instead > >>>> of having to deal with all sorts of evolving config files, everything > stays > >>>> in python. > >>>> > >>>> -- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "pylons-discuss" group. > >>>> To unsubscribe from this group and stop receiving emails from it, > send > >>>> an email to [email protected]. > >>>> To post to this group, send email to [email protected]. > > >>>> Visit this group at http://groups.google.com/group/pylons-discuss. > >>>> For more options, visit https://groups.google.com/d/optout. > >>>> > >>> > >>> -- > >>> You received this message because you are subscribed to the Google > Groups > >>> "pylons-discuss" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an > >>> email to [email protected]. > >>> To post to this group, send email to [email protected]. > >>> Visit this group at http://groups.google.com/group/pylons-discuss. > >>> For more options, visit https://groups.google.com/d/optout. > >>> > >>-- > >>You received this message because you are subscribed to the Google > Groups > >>"pylons-discuss" group. > >>To unsubscribe from this group and stop receiving emails from it, send > an > >>email to [email protected]. > >>To post to this group, send email to [email protected]. > >>Visit this group at http://groups.google.com/group/pylons-discuss. > >>For more options, visit https://groups.google.com/d/optout. > >> > > > > ------------------------ > Steve Piercy, Soquel, CA > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
