- rearrange the internals such that we no longer use global

variables to get to things.   The new structure is:

EnvironmentContext -> MigrationContext -> Operation

EnvironmentContext sets up the variables "alembic.context"
and "alembic.op" to act like the modules they used to.
MigrationContext can also exist independently of EnvironmentContext.

Refactoring is still underway here.

1 files changed, 17 insertions, 0 deletions

diff --git a/CHANGES b/CHANGES
index 05a8d86..07eb753 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,20 @@
+0.2.0
+=====
+- [feature] API rearrangement allows everything
+  Alembic does to be represented by contextual
+  objects, including EnvironmentContext,
+  MigrationContext, and Operations.   Other
+  libraries and applications can now use
+  things like "alembic.op" without relying
+  upon global configuration variables.
+  The rearrangement was done such that 
+  existing migrations should be OK, 
+  as long as they use the pattern 
+  of "from alembic import context" and 
+  "from alembic import op", as these
+  are now contextual objects, not modules.
+  [#19]
+
 0.1.2
 =====
 - [bug] fix the config.main() function to honor