head 1.1; access; symbols pkgsrc-2023Q4:1.1.0.64 pkgsrc-2023Q4-base:1.1 pkgsrc-2023Q3:1.1.0.62 pkgsrc-2023Q3-base:1.1 pkgsrc-2023Q2:1.1.0.60 pkgsrc-2023Q2-base:1.1 pkgsrc-2023Q1:1.1.0.58 pkgsrc-2023Q1-base:1.1 pkgsrc-2022Q4:1.1.0.56 pkgsrc-2022Q4-base:1.1 pkgsrc-2022Q3:1.1.0.54 pkgsrc-2022Q3-base:1.1 pkgsrc-2022Q2:1.1.0.52 pkgsrc-2022Q2-base:1.1 pkgsrc-2022Q1:1.1.0.50 pkgsrc-2022Q1-base:1.1 pkgsrc-2021Q4:1.1.0.48 pkgsrc-2021Q4-base:1.1 pkgsrc-2021Q3:1.1.0.46 pkgsrc-2021Q3-base:1.1 pkgsrc-2021Q2:1.1.0.44 pkgsrc-2021Q2-base:1.1 pkgsrc-2021Q1:1.1.0.42 pkgsrc-2021Q1-base:1.1 pkgsrc-2020Q4:1.1.0.40 pkgsrc-2020Q4-base:1.1 pkgsrc-2020Q3:1.1.0.38 pkgsrc-2020Q3-base:1.1 pkgsrc-2020Q2:1.1.0.34 pkgsrc-2020Q2-base:1.1 pkgsrc-2020Q1:1.1.0.14 pkgsrc-2020Q1-base:1.1 pkgsrc-2019Q4:1.1.0.36 pkgsrc-2019Q4-base:1.1 pkgsrc-2019Q3:1.1.0.32 pkgsrc-2019Q3-base:1.1 pkgsrc-2019Q2:1.1.0.30 pkgsrc-2019Q2-base:1.1 pkgsrc-2019Q1:1.1.0.28 pkgsrc-2019Q1-base:1.1 pkgsrc-2018Q4:1.1.0.26 pkgsrc-2018Q4-base:1.1 pkgsrc-2018Q3:1.1.0.24 pkgsrc-2018Q3-base:1.1 pkgsrc-2018Q2:1.1.0.22 pkgsrc-2018Q2-base:1.1 pkgsrc-2018Q1:1.1.0.20 pkgsrc-2018Q1-base:1.1 pkgsrc-2017Q4:1.1.0.18 pkgsrc-2017Q4-base:1.1 pkgsrc-2017Q3:1.1.0.16 pkgsrc-2017Q3-base:1.1 pkgsrc-2017Q2:1.1.0.12 pkgsrc-2017Q2-base:1.1 pkgsrc-2017Q1:1.1.0.10 pkgsrc-2017Q1-base:1.1 pkgsrc-2016Q4:1.1.0.8 pkgsrc-2016Q4-base:1.1 pkgsrc-2016Q3:1.1.0.6 pkgsrc-2016Q3-base:1.1 pkgsrc-2016Q2:1.1.0.4 pkgsrc-2016Q2-base:1.1 pkgsrc-2016Q1:1.1.0.2 pkgsrc-2016Q1-base:1.1; locks; strict; comment @# @; 1.1 date 2016.01.05.10.27.27; author wiz; state Exp; branches; next ; commitid mJd1IdVoS6lziJPy; desc @@ 1.1 log @Import py-constants-0.6.0 as devel/py-constants. Most applications use constants. Many constants take different values based on the environment the application is executed in. Think database credentials over development, testing, staging, production or stock market execution over development, testing, paper, production ... Shamelessly inspired by the app_constants_ gem, ``constants`` aims to solve that problem (and that problem only). @ text @Most applications use constants. Many constants take different values based on the environment the application is executed in. Think database credentials over development, testing, staging, production or stock market execution over development, testing, paper, production ... Shamelessly inspired by the app_constants_ gem, ``constants`` aims to solve that problem (and that problem only). @