An undocumented feature of legacy content libraries is that you can import a python_lib.zip file into them just like you can for courses, and problems in that library can then make use of that shared library code (like the excellent MIT Grading Library).
The new libraries experience does not yet support this feature. It’s something we’ll eventually want to support anyway, but we will prioritize it more highly if this feature gap is blocking people from migrating off of the legacy library experience.
To that end, if your organization uses python_lib.zip files in your content libraries, please reply on this thread.
I’m not sure. We definitely have courses that include a python_lib.zip asset and then use it in custom-graded problems, but I don’t know if we have libraries that use it (and courses that use those libraries). I don’t recall the latter coming up, but I think it would have largely been invisible for the migration to codejail-service.
What’s a good way of finding out whether there are libraries like this? I’m not very familiar with libraries and assets in general.
Normally I wouldn’t reply just to say “no”, but I did want to mention it since we do a lot of custom stuff: Harvard uses python_lib.zip files in nearly all of our courses but not in libraries. (Really, we just use one python_lib.zip file, but every course has a copy of it.)
To clarify, this would be a situation where a library has custom-graded problems, but the library then only works if it is used from a course that has an appropriate python_lib.zip?
I don’t think it was an intended feature as much as it was sharing code paths with the course import process. A python_lib.zipcan be imported into a library, but it doesn’t sync into the course or anything like that. It’s just there to be used locally by problems in the library.