google-code-export / pysal

Automatically exported from code.google.com/p/pysal
Other
1 stars 1 forks source link

legacy folders #110

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I don't think this is a pysal bug per se, but it can result in pysal not 
functioning correctly.  

The folder pysal/trunk/pysal/spatial_dynamics/markov/ and all the .py files 
inside were deleted some time ago from the repository.   However, my local hard 
drive had some .pyc files in there so subversion did not remove the folder from 
my computer.   The result is "import pysal" fails with the following error:

In [1]: import pysal
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (5, 0))

---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)

/Users/dfolch/<ipython console> in <module>()

/Users/dfolch/AAA/work/pySAL_googleCode/SVN/pysal/trunk/pysal/__init__.pyc in 
<module>()
     49 from inequality.theil import Theil,TheilD,TheilDSim
     50 from region.maxp import Maxp,Maxp_LISA
---> 51 from spatial_dynamics import Markov, Spatial_Markov, LISA_Markov, 
SpatialTau, Theta
     52 from spatial_dynamics import ergodic
     53 from weights import W,lat2W,regime_weights,comb,full,shimbel,order,higher_order,remap_ids

ImportError: cannot import name Spatial_Markov

I know that the solution is to simply delete this old folder.  However, a user 
came to me today not understanding why "import pysal" stopped working after 
updating their local repository.  And the error returned by python does not 
immediately point to this folder as the troublemaker.

Original issue reported on code.google.com by dfo...@gmail.com on 30 Jul 2010 at 1:09

GoogleCodeExporter commented 9 years ago

Original comment by sjsrey on 31 Jul 2010 at 2:17

GoogleCodeExporter commented 9 years ago
This is an SVN issue.  SVN is set to ignore pyc files so it think they are 
private files and does not delete them.  You can safely remove the dead files 
manually.  You can use the `svn stat` commend to help find dead files.

Original comment by schmi...@gmail.com on 3 Jan 2011 at 6:22