This is my first time digging into buildout code, so the tests may not
be optimal. I wanted to assert that the sys.path entries are
modified, but I was having a hard time getting and buildout.develop or
buildout.eggs to show up (probably because I am not doing a full
recipe.install()). Therefore, I am merely testing for the definition
of the `base` variable that buildout will create when
relative-paths=True.
Definitely! Here is a first past with 2 additional tests: bazaar. launchpad. net/~johnpaulet t/djangorecipe/ relative- paths/revision/ 113
http://
This is my first time digging into buildout code, so the tests may not paths=True.
be optimal. I wanted to assert that the sys.path entries are
modified, but I was having a hard time getting and buildout.develop or
buildout.eggs to show up (probably because I am not doing a full
recipe.install()). Therefore, I am merely testing for the definition
of the `base` variable that buildout will create when
relative-
On Sun, Jun 26, 2011 at 8:31 AM, roland <email address hidden> wrote: /code.launchpad .net/~johnpaule tt/djangorecipe /relative- paths/+ merge/65888
> Thank you for this patch.
> Could you write unittests to go with it?
>
>
> --
> https:/
> You are the owner of lp:~johnpaulett/djangorecipe/relative-paths.
>