SciPy SVN altered so that newscipy and newcore are now the trunk.
I've finished altering the subversion repository of SciPy so that the new development is taking place on the trunk of both scipy and scipy_core. The old versions are under branches named oldcore and oldscipy. Get the new repositor(y,ies) using: *Core*: svn co http://svn.scipy.org/svn/scipy_core/trunk core *Full SciPy*: svn co http://svn.scipy.org/svn/scipy/trunk scipy Doing both will place two directories named core and scipy in your current directory containing the current state of both repositories. python setup.py install should work in each directory. The Freeze is now over. I want to track down the bug that Christopher Hanley noted and another f2py-related bug before making a release, which I expect to happen by the weekend. -Travis
Travis Oliphant <oliphant@ee.byu.edu> writes:
I've finished altering the subversion repository of SciPy so that the new development is taking place on the trunk of both scipy and scipy_core.
The old versions are under branches named oldcore and oldscipy.
Get the new repositor(y,ies) using:
*Core*: svn co http://svn.scipy.org/svn/scipy_core/trunk core
*Full SciPy*: svn co http://svn.scipy.org/svn/scipy/trunk scipy
Doing both will place two directories named core and scipy in your current directory containing the current state of both repositories.
Alternatively, instead of doing a full checkout, you can switch your working copies: Within your (old) newcore directory: svn sw http://svn.scipy.org/svn/scipy_core/trunk and same for full scipy. -- |>|\/|< /--------------------------------------------------------------------------\ |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ |cookedm@physics.mcmaster.ca
participants (2)
-
cookedm＠physics.mcmaster.ca -
Travis Oliphant