Is there a good way to do version control when developing pylons applications with dependencies?
The only reasonable way to do what you want is to have application B work against formal releases of application A, even if those releases are labled beta or release candidate. IOW, do not treat application A as source code, but as an imported module installed with setup.py or other means.
Doing it this way will let you move application B from one well known stage of A to the other, plus you'll be able to report bugs or incompatibilities against specific releases, and go back to previous releases when a new A breaks B.
I'm developing two pylons applications at the same time. Application B uses a lot of the controllers, etc. in application A. Both applications are under active development, but for administrative reasons, they have to be kept separate.
Is there a convenient way to do version control so that changes to A are easy to pull into B?  It'd be great if there were a way to do this with svn, since it already plays nice with pylons and paster.