Carlos Ribeiro wrote:
If none of your users volunteers to do the build for you, I would stop
worrying about the Windows users.
Sorry, Martin. I understand your point, but I think you are not being
realistic. I for myself took the decision to use only free tools for
my own development, but I still have to suport my Windows customers. I
can't force them to change to Linux. I don't own a copy of MSVC. Also,
one of the reasons to choose a third part module is to save time. The
moment I am required to recompile everything myself I'm losing this
convenience. This of course impacts my ability to focus on my own
work, and so the story goes.
I did not suggest that *all* your Windows users should recompile
your module - just a single one would be sufficient.
I'm not saying that module authors should work for free just to save
me some time & hassle. It's fair if an author decides to release a
Linux-only module. But again -- this is not realistic. The world has a
lot of Windows users, and I depend on them for my own income. If I
can't find a good set of Python tools for my projects, what should I
do? Picking another language is not a choice, mind you :-)
As I said: Find a volunteer that has the necessary build infrastructure,
and have that volunteer build the extension for you.
The dream scenario is not to
require recompiling, at least inside the same major release (2.4 to
2.5, for example). That would be really great.
That is guaranteed. Extensions built for 2.4 will certainly continue
to work in 2.4.1, and later 2.4.x. They will stop working with 2.5
(as they are linked with python24.dll).
Regards,
Martin
_______________________________________________
Python-Dev mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
