This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

# Tired of Resource OverlaYs

### Pointers

### Installation Notes

At this stage, the devel branches of saga-python, radical.utils, and bigjob should be used with TROY. (If these are not manually installed, the TROY installer may pull in non-devel versions.)

To set up the TROY environment, use

pip install .

Or, to make extra-sure TROY is installed correctly with all trace of previous installations removed:

pip uninstall troy; rm -rf ./build; pip install .

### Configuration

You can use a configuration file in the location “~/.troy.cfg”. An example is provided in examples/troy.cfg, you can copy that to “~/.troy.cfg” and customize to your environment.

Available configuration options are explained in more detailed in the Troy library documentation, and apply mostly to the Troy plugins.

### Note to developers:

The development branch is devel, all developers should branch off ‘devel’ when implementing new features. Feature branches are named feature/xyz, and are only merged into devel after coordinating with the other developers.

Releases are tagged on the master branch – only the release manager will merge from devel to master, to prepare for a release.

An usual development workflow should look like:

` git clone git@github.com:saga-project/troy.git # get repostory cd troy                                        # git checkout devel                             # switch to devel branch git checkout -b feature/world_domination       # create a feature branch from there vim troy/world_domination.py                   # do the deed... vim tests/test_world_domination.py             # git commit -am 'we now dominate the world'     # commit your changes git push origin feature/world_domination       # sync with github `

The last command will ensure that your (until then only locally existing) branch will be mirrored in the central repository, and is available for other developers.

Once the group agreed on merging, you would run:

` git checkout devel git pull                               # get updates from github git checkout feature/world_domination git pull                               # get updates from github git merge devel                        # make sure branch is in sync with devel run_my_tests                           # do it! git checkout devel git merge feature/world_domination     # merge your feature branch git push origin                        # sync with github git branch -d feature/world_domination # remove feature branch `

If unsure about anything, ask Andre ;)

Release History

Release History

0.0.3

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
troy-0.0.3.tar.gz (215.7 kB) Copy SHA256 Checksum SHA256 Source Mar 3, 2014

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting