On Thu, Feb 19, 2009 at 7:57 AM, David Stanek wrote:
> On Thu, Feb 19, 2009 at 7:10 AM, Jeff Dyke wrote:
>> Fair enough. Say my project is called foo, and it has many
>> submodules. So there are imports that may look like `import foo.bar`
>> or `from foo.bar import baz`, if i change the top lev
On Thu, Feb 19, 2009 at 7:10 AM, Jeff Dyke wrote:
> Fair enough. Say my project is called foo, and it has many
> submodules. So there are imports that may look like `import foo.bar`
> or `from foo.bar import baz`, if i change the top level directory, it
> is no longer foo and then those imports
Ah, OK. I have never worked like that. The only helpful comment I can
think of is that I believe svn will store links correctly (while CVS
doesn't).
However, I do find the whole approach a bit odd. You seem to be doing
your own versioning "by hand" (having two packages that are equivalent
with
Fair enough. Say my project is called foo, and it has many
submodules. So there are imports that may look like `import foo.bar`
or `from foo.bar import baz`, if i change the top level directory, it
is no longer foo and then those imports do not work as originally
written. The way i currently do
maybe this is just me, but i don't have a clue what your problem is. what
does "starting imports all over the place" mean? what do you mean by
"retired"?
i use svn with python in exactly the same way as with java (and, i
thought, in the same way as anyone uses svn with any language; java uses
t
