ÿØÿàJFIFÿþ ÿÛC       ÿÛC ÿÀÿÄÿÄ"#QrÿÄÿÄ&1!A"2qQaáÿÚ ?Øy,æ/3JæݹÈ߲؋5êXw²±ÉyˆR”¾I0ó2—PI¾IÌÚiMö¯–þrìN&"KgX:Šíµ•nTJnLK„…@!‰-ý ùúmë;ºgµŒ&ó±hw’¯Õ@”Ü— 9ñ-ë.²1<yà‚¹ïQÐU„ہ?.’¦èûbß±©Ö«Âw*VŒ) `$‰bØԟ’ëXÖ-ËTÜíGÚ3ð«g Ÿ§¯—Jx„–’U/ÂÅv_s(Hÿ@TñJÑãõçn­‚!ÈgfbÓc­:él[ðQe 9ÀPLbÃãCµm[5¿ç'ªjglå‡Ûí_§Úõl-;"PkÞÞÁQâ¼_Ñ^¢SŸx?"¸¦ùY騐ÒOÈ q’`~~ÚtËU¹CڒêV  I1Áß_ÿÙ M!Vc@sdZddlmZddlmZddlmZddlmZyddl m Z e dWn?ej Z e j dZ ee ed e d d ZnXed ej d jjZdZdZdZejrenedS(s|Pylons bootstrap environment. Place 'pylons_config_file' into alembic.ini, and the application will be loaded from there. i(tcontext(tloadapp(t fileConfig(tEngine(tconfigt__file__tpylons_config_files config:%st relative_tot.s %s.model.metaspylons.packagecCsCtjdtjjdtdttjtjWdQXdS(sFRun migrations in 'offline' mode. This configures the context with just a URL and not an Engine, though an Engine is acceptable here as well. By skipping the Engine creation we don't even need a DBAPI to be available. Calls to context.execute() here emit the given string to the script output. turlttarget_metadatat literal_bindsN( Rt configuretmetatengineR R tTruetbegin_transactiontrun_migrations(((sM/opt/alt/python27/lib/python2.7/site-packages/alembic/templates/pylons/env.pytrun_migrations_offline$s  c CsXtdtj:}tjd|dttjtjWdQXWdQXdS(sRun migrations in 'online' mode. In this scenario we need to create an Engine and associate a connection with the context. s'Please specify engine connectivity heret connectionR N(tNotImplementedErrorRtconnectRR R RR(R((sM/opt/alt/python27/lib/python2.7/site-packages/alembic/templates/pylons/env.pytrun_migrations_online7s   N(t__doc__talembicRt paste.deployRtlogging.configRtsqlalchemy.engine.baseRtpylonsRt pylons_configtget_main_optiont config_filetwsgi_appt __import__tmodelR tNoneR RRtis_offline_mode(((sM/opt/alt/python27/lib/python2.7/site-packages/alembic/templates/pylons/env.pyts&