stpeterperhaps 'xsf' needs to own that one, too (not just calgen)?
KevOh, you need to install stuff in there?
KevI thought I'd got that one all working.
stpeterwhen I tried 'pip install icalendar' I got that error
KevWhy does the difftool need icalendar?
stpeterask Tobias :-)
KevI thought I had the difftool working - what's broken?
dwdhas left
Kevstpeter: What caused you to want to install icalendar into the difftool's virtualenv?
stpeterum
stpeterI didn't want to
KevOh.
KevAh.
stpeterI probably don't understand virtualenv
KevI think you're doing half of what Bear suggested, and not what I suggested.
stpeterI did 'pip install icalender' at /usr/local/virtualenv/calgen but perhaps that's not right
KevIf you want to run a script in the calgen virtualenv, just make the shebang into #!/usr/local/virtualenv/calgen/bin/python
KevYes, that's not right.
KevCompletely ignore what Bear said :)
stpeterk :-)
stpeterheh
stpeterah, ok
bearyes, I was wrong to interject - apologies
stpeterbear: no worries!
KevBear was giving advice based on us being fluent in Python :)
KevIf you want to install packages into the calgen virtualenv, use /usr/local/virtualenv/calgen/bin/easy_install THE_THING. You could use /usr/local/virtualenv/calgen/bin/pip instead, but I habitually use easy_install and always have.
stpeterok
stpeterwell, I still have issues:
$ ./calgen.py
Traceback (most recent call last):
File "./calgen.py", line 45, in <module>
from icalendar import Calendar, Event, Alarm, UTC, vText
ImportError: cannot import name UTC
but I've made progress
KevThe reason we use multiple virtualenvs is to avoid screwing up e.g. the difftool when we're installing packages for calgen. Or whatever.
stpetersure, makes perfect sense
KevThat suggests to me a change in the icalendar package.
Kev(If the package was completely missing, I wouldn't have expected the other imports to succeed)
KevThis is where bear is likely to be useful :)
bearthat is a version mismatch (smells like a version mismatch)
stpeterright, that's what I was thinking
bearare you running python v3 and not noticing
bearbecause UTC was renamed to Utc in the python v3 package
bearof icalendar
stpeterheh nice
KevPython 2.7.3 (default, Mar 13 2014, 11:03:55)
bearyea, 2.7+ picks up a lot of v3 changes
bearso change the code to import Utc instead of UTC
stpeterok, well, something to investigate a bit later
bearsorry - in non python speak... library maintainers like to keep their source running in python v2.7 like it is in python v3 as that makes their life easier
KevI got that :)
stpeterah yes, "Renamed the UTC class to Utc, so it would not clash with the UTC object, since that rendered the UTC object unpicklable." https://github.com/collective/icalendar/blob/master/CHANGES.rst
Kevstpeter: I think all you need to do is edit the import line in Tobias's script. I can do this if you'd like.
stpeteryeah I tried that already but it's still not happy, we might multiple versions installed or something strange, checking
stpeteroh well, I think this will be an evening project, I need to do some paying work :-)