On Fri, May 18, 2012 at 11:37 AM, Rajeev Singh <rajs2...@gmail.com> wrote:
> Hi,
> I have installed the shedskin-0.9.2 and ran all the tests. Two of the tests
> failed -
> *** tests failed: 2
> [196, 199]
> Is it a known isssue? I am on a Debian machine and tried with both
> python-2.6 and 2.7.
> Rajeev
> --
> You received this message because you are subscribed to the Google Groups
> "shedskin-discuss" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/shedskin-discuss/-/C-EQkuPXIwoJ.
> To post to this group, send email to shedskin-discuss@googlegroups.com.
> To unsubscribe from this group, send email to
> shedskin-discuss+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/shedskin-discuss?hl=en.
For 199 -
$ python 199.py > 199_python_out
Traceback (most recent call last):
File "199.py", line 12, in <module>
decompressor(open('testdata/binas', 'rb'))
IOError: [Errno 2] No such file or directory: 'testdata/binas'
On Tue, May 29, 2012 at 5:09 AM, Mark Dufour <mark.duf...@gmail.com> wrote:
> hi rajeev,
> sorry for the delayed reply!
> what errors/differences do you see when running these tests
> separately..? (e.g. shedskin 196 && make && ./196 compared to python
> 196.py).
> thanks for mentioning in any case,
> mark.
> On Fri, May 18, 2012 at 11:37 AM, Rajeev Singh <rajs2...@gmail.com> wrote:
>> Hi,
>> I have installed the shedskin-0.9.2 and ran all the tests. Two of the tests
>> failed -
>> *** tests failed: 2
>> [196, 199]
>> Is it a known isssue? I am on a Debian machine and tried with both
>> python-2.6 and 2.7.
>> Rajeev
>> --
>> You received this message because you are subscribed to the Google Groups
>> "shedskin-discuss" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/shedskin-discuss/-/C-EQkuPXIwoJ.
>> To post to this group, send email to shedskin-discuss@googlegroups.com.
>> To unsubscribe from this group, send email to
>> shedskin-discuss+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/shedskin-discuss?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "shedskin-discuss" group.
> To post to this group, send email to shedskin-discuss@googlegroups.com.
> To unsubscribe from this group, send email to shedskin-discuss+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/shedskin-discuss?hl=en.
apparently sys.platform returns 'linux3' with your version of python,
where shedskin always returns 'linux2' under linux. on my system,
sys.platform also returns 'linux2' with cpython, even though I'm on
linux 3.. anyone interested in looking into this?
> $ python 199.py > 199_python_out
> Traceback (most recent call last):
> File "199.py", line 12, in <module>
> decompressor(open('testdata/binas', 'rb'))
> IOError: [Errno 2] No such file or directory: 'testdata/binas'
ah ok, this is because I forgot to commit this test file to GIT
earlier. so that's no real problem either..
> apparently sys.platform returns 'linux3' with your version of python,
> where shedskin always returns 'linux2' under linux. on my system,
> sys.platform also returns 'linux2' with cpython, even though I'm on
> linux 3.. anyone interested in looking into this?
On Sun, Jun 3, 2012 at 10:55 PM, Mark Dufour <mark.duf...@gmail.com> wrote:
>> Nope, this is a python bug and fixed in newer releases - it seems
>> debian needs an update :)
>> http://hg.python.org/cpython/rev/c816479f6aaf
> it's also a shedskin bug.. :-)
> in lib/sys.cpp:
> #ifdef __linux__
> platform = new str("linux2");
> #endif
AFAIK, for python2 this is just fine. Just python3 needs to be
"linux", but as shedskin doesn't support that anyway, it's not a but
(yet) :)
> AFAIK, for python2 this is just fine. Just python3 needs to be
> "linux", but as shedskin doesn't support that anyway, it's not a but
> (yet) :)
yeah, it's not very important, but the test fails on an easily fixable
difference between cpython and shedskin behaviour.. so I consider it a
(minor) bug.