XMPP Council - 2014-03-26

Unless the Editors get back to me, I don't think we have anything that we need to discuss today.

Kev: BTW m&m sends his regrets

or sent

or something

Ta.

Not that he's obliged to turn up :)

have you folks changed to Summer Time yet?

No.

ah ok

You mean Wrong Time?

I admit that I keep a few clocks on standard time :-)

stpeter, like the oven clock :P

Probably this weekend that Sweden goes silly time. Last weekend in Mars or somesuch.

Zash, yeah...on the 30th

at least in DE

Standardized by the EU? :)

I believe it's consistent across Europe, at least.

'tis time, 'tis time.

here

Should be short, as I think we have no agenda.

1) Roll call.

Tobias: Too eager :p

here

:)

Tobias is using the new FTL transport

XMPP-over-Neutrinos.

Kev, your connection is too laggy...i bet you've already typed it in ✏

:)

MattJ: Here?

Here

MattJ: There?

There also

I don't remember Fippo sending apologies, will check the logs.

2) Date of next.

I can ping Fippo if needed :-)

stpeter: I did so.

I think we move to 17:00Z next week, yes?

Yes

Everyone OK with that?

fine with me

I'll take that as a yes.

I'll update the calendar events

3) Any other business.

stpeter: Ta.

haven't received any comments or questions on the IoT Discovery proposal

Anticipating Peter's question about discovery - it was presented to Council last week. Objection period ends next Wednesday.

speaking of which, I need to ping Tobias about getting the right code onto perseus.jabber.org so that we can run calgen.py

if you have any, please send them to me

And he still beat me :/

:)

stpeter, can have a look at it later today

stpeter: I can probably sort that out, if you tell me what you need.

OK, I think we're done then.

Thanks all.

(y)

the icalendar python lib is missing at the least, not sure what else because I got distracted from testing :-)

I'll make you a virtualenv now.

virtualenv rings a bell...i've either used it for gen.py or calgen.py or both

stpeter: There is now a virtualenv in /usr/local/virtualenv/calgen with icalendar installed.

Kev: thanks!

It's owned by the xsf user, so if you need anything else in it, you can /usr/local/virtualenv/calgen/bin/easy_install THAT_THING.

if the virtualenv is active it will have pip in the local path

so "pip THAT_THING" will be all that is required

bear: I think 'activating' virtualenvs is just going to cause us pain, compared to using them explicitly.

YMMV, what with me not being a Python person.

it can be done in any scripts and it *really* is the sanest way

In scripts, yes.

But doing it in a shell, I don't think is a good idea.

I should be able to help craft scripts and the .profile stuff to make it happen for logins

". bin/activate"

that's all you need to type

I understand the mechanics.

I think it's a bad idea.

It just encourages you to slip and install the wrong thing in the wrong place.

ah

that's is a common view for non-python folks who don't spend all day in venvs

As I said.

sorry - distracted and tired bear is ... distracted and tired

I can relate.

I note that I screwed up the timezone switch, and I think what we meant to agree to was a move to 15:00Z, not to 17:00Z.

Heh

OSError: [Errno 13] Permission denied: '/usr/local/virtualenv/hg/build'

perhaps 'xsf' needs to own that one, too (not just calgen)?

Oh, you need to install stuff in there?

I thought I'd got that one all working.

when I tried 'pip install icalendar' I got that error

Why does the difftool need icalendar?

ask Tobias :-)

I thought I had the difftool working - what's broken?

stpeter: What caused you to want to install icalendar into the difftool's virtualenv?

um

I didn't want to

Oh.

Ah.

I probably don't understand virtualenv

I think you're doing half of what Bear suggested, and not what I suggested.

I did 'pip install icalender' at /usr/local/virtualenv/calgen but perhaps that's not right

If you want to run a script in the calgen virtualenv, just make the shebang into #!/usr/local/virtualenv/calgen/bin/python

Yes, that's not right.

Completely ignore what Bear said :)

k :-)

heh

ah, ok

yes, I was wrong to interject - apologies

bear: no worries!

Bear was giving advice based on us being fluent in Python :)

If 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.

ok

well, 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

The reason we use multiple virtualenvs is to avoid screwing up e.g. the difftool when we're installing packages for calgen. Or whatever.

sure, makes perfect sense

That suggests to me a change in the icalendar package.

(If the package was completely missing, I wouldn't have expected the other imports to succeed)

This is where bear is likely to be useful :)

that is a version mismatch (smells like a version mismatch)

right, that's what I was thinking

are you running python v3 and not noticing

because UTC was renamed to Utc in the python v3 package

of icalendar

heh nice

Python 2.7.3 (default, Mar 13 2014, 11:03:55)

yea, 2.7+ picks up a lot of v3 changes

so change the code to import Utc instead of UTC

ok, well, something to investigate a bit later

sorry - 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

I got that :)

ah 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

stpeter: I think all you need to do is edit the import line in Tobias's script. I can do this if you'd like.

yeah I tried that already but it's still not happy, we might multiple versions installed or something strange, checking

oh well, I think this will be an evening project, I need to do some paying work :-)