<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 30 Dec 2014, at 19:26, John Swinbank <<a href="mailto:swinbank@princeton.edu" class="">swinbank@princeton.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br class=""><blockquote type="cite" class="">On 29 Dec 2014, at 20:03, John D. Swinbank <<a href="mailto:swinbank@Princeton.EDU" class="">swinbank@Princeton.EDU</a>> wrote:<br class=""></blockquote><br class=""><br class=""><blockquote type="cite" class="">As a longer term solution, I ran 2to3 on mksetup then added a “from __future__ import print_function”, and can now install EUPS with both Python 2.7 & 3.4. I can’t decide if that’s the right solution, or if it would be better to force the —with-python option to also apply to mksetup. Thoughts?<br class=""></blockquote><br class="">I thought about this a little more, decided the latter was a simpler option, and filed DM-1730 on JIRA together with accompanying PR against EUPS. The fix is straightforward.<br class=""><br class="">Cheers,<br class=""><br class="">John<br class="">_______________________________________________<br class="">dm-users mailing list<br class=""><a href="mailto:dm-users@lists.lsst.org" class="">dm-users@lists.lsst.org</a><br class="">https://lists.lsst.org/mailman/listinfo/dm-users<br class=""></div></blockquote></div><br class=""><div class="">John,</div><div class=""><br class=""></div><div class="">thanks for fixing this!</div><div class=""><br class=""></div><div class="">I followed your advice and switched to Python 2 for now.</div><div class=""><br class=""></div><div class="">Now the ran into this error … the doxygen build fails with a compiler error:</div><div class=""><a href="https://gist.github.com/cdeil/3070715137ac799fcd41" class="">https://gist.github.com/cdeil/3070715137ac799fcd41</a></div><div class=""><br class=""></div><div class="">I do have doxygen 1.8.7 from Macports at /opt/local/bin/doxygen and on my PATH, is it really useful to build a separate one from source?</div><div class=""><br class=""></div><div class="">Another issue I noticed is that it’s not possible to blow away the LSST software folder with rm -r … I think the reason is that I don’t have write permissions for the eups/python folder.</div><div class="">Can you change this so that I don’t have to fiddle with chmod or sudo?</div><div class=""><br class=""></div><div class="">$ rm -r eups<br class="">rm: eups/python/eups/__init__.py: Permission denied<br class="">$ ls -lh eups/<br class="">total 80<br class="">-rw-r--r-- 1 deil staff 1.2K Dec 29 23:01 README<br class="">-rw-r--r-- 1 deil staff 35K Dec 29 23:01 Release_Notes<br class="">dr-xr-xr-x 3 deil staff 102B Dec 29 23:01 python<br class="">drwxr-xr-x 2 deil staff 68B Dec 29 23:01 site<br class="">drwxr-xr-x 3 deil staff 102B Dec 29 23:01 ups<br class=""><br class=""></div><div class="">Cheers,</div><div class="">Christoph</div></body></html>