No problem. The reason is that you can put your actual credentials in the secrets.py file and test it with a real provider.
Requiring user to copy secrets.py-dist over to secrets.py makes it harder to edit the wrong file and accidentally check in your real credentials. On Sun, Oct 28, 2012 at 8:08 AM, Jaume Devesa <[email protected]>wrote: > Good, thanks! > > Sorry if I insist but, why we need to copy from 'secrets.py-dist' to > 'secrets.py'? Couldn't the file be named 'secrets.py' directly? Maybe the > reason is obvious but I can not see it... > > On 28 October 2012 15:40, Tomaž Muraus <[email protected]> wrote: > > > Done, thanks! > > > > secrets.py was actually already there, but not a long time ago we've > moved > > the test directory from test/ to libcloud/test and forgot to update the > > .gitignore file. > > > > On Sun, Oct 28, 2012 at 5:12 AM, Jaume Devesa <[email protected] > > >wrote: > > > > > Hi, > > > > > > Just a trivial patch. So trivial that I didn't even create a Jira (let > me > > > know if it is needed) > > > > > > When run *tox* to check the tests for all python versions, you need to > > > copy the *libcloud/test/secrets.py-dist* into the * > > > libcloud/test/secrets.py* file. I ignore why, can somebody explain me? > > > > > > Anyway, atfer that, the *tox* execution creates a *.tox/* directory > where > > > it saves the generated 'virtualenvs' and execution logs. > > > > > > The patch just mentions the '*secrets.py*' file and the *.tox/* > directory > > > in the .*gitignore* file to avoid put these files into version control. > > > > > > Regards, > > > jaume > > > > > >
