From 93c6816e64c916588ff35013ba2b4a0dac73411e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Eray=20=C3=96zkural?= <eray@pardus.org.tr>
Date: Fri, 12 Aug 2005 20:02:24 +0000
Subject: [PATCH] * bu da import olayini acikliyor

---
 pisi/cli/README | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 pisi/cli/README

diff --git a/pisi/cli/README b/pisi/cli/README
new file mode 100644
index 00000000..665fb4c9
--- /dev/null
+++ b/pisi/cli/README
@@ -0,0 +1,21 @@
+Writing commands:
+-----------------
+
+Subclass from Command.
+
+Be careful not to import PiSi modules before Command is run, e.g.
+do it in run() method. This is necessary to prevent an obscure
+initialization error.
+
+We used to import pisi.operations in pisi.cli
+
+This prevented pisi.operations from having the current global
+pisi.ui.ui because it's loaded before the UI is set! So, despite
+what you might understand from the python FAQ 1.2.3
+http://www.python.org/doc/faq/programming.html#how-do-i-share-global-variables-across-modules
+you have to be careful about the initialization order when using
+singleton modules.
+
+Another way to solve this is to ensure that the global module is
+always imported again in every function it is called (see
+ui.CLI.confirm() ) but this is more expensive.