Open GoogleCodeExporter opened 9 years ago
This would involve maintaining working versions of various dependencies
including numpy and nltk, perhaps in an optional subdirectory of CAVaT, and
then adding the dependency path (if present) to the module search path. We'd
also require two packages of CAVaT - one standard, one including all the deps.
De-prioritised in favour of providing helpful installation instructions for
CAVaT dependencies, for each operating system.
Original comment by l...@dcs.shef.ac.uk
on 3 Aug 2011 at 12:32
Original issue reported on code.google.com by
leonderczynski
on 28 May 2010 at 2:49