Bump ORA version to 0.2.7.

[cahrens]

No description provided.

[nedbat]

Now would be a fine time to remove the -e.

[cahrens]

@nedbat
What does it mean to remove the "-e"? Why was it there before, and why do we no longer need it?

[nedbat]

The -e means, install as an editable working tree. We never needed it, it's been cargo-culted from the beginning. It's allowed us to have bugs in our setup.py files that we don't find until much later.

The instructions at the top of the file were an attempt to get people to stop using it. :)

[cahrens]

@nedbat thanks. I would think you knew by now that nobody reads the instructions at the top of the file (unless the thing they are changing is at the top of the file). :)

[cahrens]

jenkins run bokchoy

[nedbat]

The test failures are because of the errors in ora's setup.py: it doesn't name all of the packages that it should.

[cahrens]

Thanks, @nedbat. So does ora2 need to declare EVERY package it has? Is there no concept of "private" packages?

For instance, there is an init file in openassessment/assessment/migrations, but it seems odd to declare that as a package.

See openedx/edx-ora2#865

[nedbat]

If you want the code to be installed when the kit is installed, then it needs to be in the packages list. That's all that list is for: what packages are in the kit, and need to be copied during installation. Many people avoid an explicit list of packages by doing this:

from setuptools import find_packages
...
setup(
    ....
    packages=find_packages(),
    ...
)

Some people exclude certain packages, but there it isn't required.

[cahrens]

jenkins run lettuce

[cahrens]

jenkins run bokchoy