On Jun 8, 2011, at 7:11 PM, Scott Cherf wrote:

Hi Glyph -

Hi Scott; I re-Cc'd the mailing list since you appear to have unintentionally replied off-list. (Sorry if you meant this to be private for some reason, but it didn't look like that to me.)

Well I re-installed python, this time version 2.7. I installed once from MacPorts and once using the .dmg distribution from python.org. Unfortunately neither install corrected the problem. Later I read the README file and discovered Twisted isn't supposed to work with Python 2.7 so I re-installed 2.6 from MacPorts. I couldn't find a 2.6 distribution on the python.org site but I didn't really look hard either.

I don't believe that this is a Python issue; and it's definitely not a Twisted issue, as the minimal example reproduces it with no Twisted at all.

Using the fresh python 2.6 installed at /opt/local/bin/python I observed the following:

[alphonse:tags/release/Twisted] cherf% python
Python 2.6.6 (r266:84292, Jun 8 2011, 18:50:17)
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> skt = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
>>> skt.bind("some.socket")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<string>", line 1, in bind
socket.error: [Errno 22] Invalid argument
>>>

I've also attached an rtf containing the results of performing a 'run -v' from the CalanderServer 2.5 directory right after re-installing python 2.6. I didn't use run -s before I did it so it shows a stripped down list of warnings, I thought some of them might be pertinent.

I don't think any of them were relevant.

Not being familiar with python (or Twisted) I'm at a loss. I can say that AFAIK the python 2.6 install is vanilla. I'm a Perl/Objective C guy and I've only started to become acquainted with python as a result of putting up MOD_PYTHON for Trac in Apache.

Again, based on what I can see here, this is definitely not Twisted, and probably not Python.

Any clues or suggestions appreciated and I'll just keep banging my head in private otherwise...

How about writing a short C program to do the same thing? If that fails, something is messed up on your system and that has nothing to do with any of this code. If it succeeds, then we know that there's some kind of issue specifically with Python and we can dig deeper.

"three man teams, radio silence, weapons-free rules of engagement"? Indeed! :)

Quite so. Those tickets stand no chance.

Regards,
Scott.