ASE Manual Release 3.6.1.2825 CAMd - CampOS Wiki

ASE Manual, Release 3.6.1.2828
Former committers:
anro Anthony Goodrow anro:fysik,dtu,dk
carstenr Carsten Rostgaard carstenr:fysik,dtu,dk
hanke Felix Hanke F,Hanke:liverpool,ac,uk
s042606 Janosch Michael Rauba s042606:fysik,dtu,dk
s052580 Troels Kofoed Jacobsen s052580:fysik,dtu,dk
11.1.3 Python 3 strategy
• One codebase for both 2 and 3.
• Use “print(...)” if possible:
print ’bla bla’ # no
print(’bla bla’) # yes
print ’bla bla:’, x # no
print(’bla bla: %s’ % x) # yes
• Don’t do this: print >> f, .... Use f.write(... + ’\n’) or ase.utils.prnt(...,
file=f).
• More help here: http://packages.python.org/six/
11.1.4 Using version control (SVN)
The version control system used in ASE development is subversion. A thorough subversion manual can be found
at http://svnbook.red-bean.com/, here is a brief overview of the most basic features needed when developing ASE.
• perform svn checkout of ase.
Place it, for example, in ase-svn directory:
cd
svn checkout https://svn.fysik.dtu.dk/projects/ase/trunk ase-svn
This retrieves the code tree from the subversion repository. Prepend PYTHONPATH and PATH environment
variables as described at Installation.
• Updating the working copy of the code (in the directory ase-svn):
svn update
After each (important) update, remove ase/svnrevision.py* files, and run:
python setup.py sdist
to keep the ase/svnrevision.py file up-to-date.
• Checking the status of the working copy (in the directory ase-svn):
svn stat
The status about the files which are not in version control can be surpassed with the -q flag, and the status
with respect to latest additions in server can be checked with the -u flag.
• Committing the changes to the repository
Before sending the changes in the working copy to the repository, working copy should be updated. After
that, the changes can be send with:
svn commit -m "Message to describe the committed changes"
If the -m option is omitted, an editor is opened for writing the log message.
188 Chapter 11. ASE development