I'm considering dropping windows support with shedskin 0.4. if you'd
like to volunteer to maintain the windows version of shedskin, please
let me know.
mark.
:-)
Is it only a packaging task?
--
Jérémie
http://www.reddit.com/r/Python/comments/bc34w/shedskin_the_python_to_c_converter_needs_a
:-)
Is it only a packaging task?
--
You received this message because you are subscribed to the Google Groups "shedskin-discuss" group.
To post to this group, send email to shedskin...@googlegroups.com.
To unsubscribe from this group, send email to shedskin-discu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/shedskin-discuss?hl=en.
I really enjoy cool piece of software like ShedSkin that is really easy to get and use in Linux but has no windows version.
This is where the Windows people just have to step up and help out. If
people use a platform, whether it's Windows, Linux, Mac OS X, Solaris
or even the delights of AIX or HP-UX, they can't expect you to run
around making sure it works on all of them, let alone provide a one-
click installer. Open source is about having to unroll the red carpet
yourself sometimes. :-)
Paul
P.S. I had some helpful advice on Shed Skin packaging for Debian, but
I'm currently stalled doing other things. One important thing which is
hopefully resolved is the licensing: is everyone's code now accounted
for and licensed suitably? That would be a big Debian show-stopper
otherwise.
P.S. I had some helpful advice on Shed Skin packaging for Debian, but
I'm currently stalled doing other things. One important thing which is
hopefully resolved is the licensing: is everyone's code now accounted
for and licensed suitably? That would be a big Debian show-stopper
otherwise.
I've done some hacking over the weekend and have shedskin working
'well' under windows using MSVC C++ 2010 Express edition (almost
certain that MSVC 2008 will NOT work due to template and STL support).
- I don't see an issue with supporting MinGW and MSVC -- I'd simply go back and change some of the 'ifdef WIN32's to ifdef _MSC_VER in places that are specific to MSVC- 3 underscores should be fine and yes would probably look nicer :)- Haven't tried an extension module -- will do so and let you know how it goes.Andy
I guess it may be the result of the 'U' not being removed from the
parameter string given to fopen()...
Unfortunately, I can't test on Windows. May someone test the attached
patch, please?
Note: I also fixed two compilation issues in builtin.hpp
If you are OK with the direction I'm taking with the Windows support then I'm happy to review the library support in general as there are certainly issues to be resolved (I 'def' out quite a bit of code in os and sys)...