Christian Hudon added the comment:
Actually, the only optparse test failing on jython 2.7 beta 1 currently is the
one that relies on sys.getrefcount. Adding a test_support.impl_detail() guard
makes all the tests pass. (See attached patch.)
I'd propose adding this patch to both the python3 and
A.M. Kuchling added the comment:
Patch to add impl_detail() looks fine to me.
--
versions: +Python 2.7, Python 3.5 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1704474
___
Roundup Robot added the comment:
New changeset a1ef419c0cfb by Andrew Kuchling in branch '2.7':
#1704474: mark refleak test as specific to CPython
http://hg.python.org/cpython/rev/a1ef419c0cfb
--
nosy: +python-dev
___
Python tracker
Roundup Robot added the comment:
New changeset c76d782cb9df by Andrew Kuchling in branch '3.4':
#1704474: mark refleak test as specific to CPython
http://hg.python.org/cpython/rev/c76d782cb9df
--
___
Python tracker rep...@bugs.python.org
A.M. Kuchling added the comment:
Committed to 2.7, 3.4, and default. Thanks for your patch!
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1704474
Christian Hudon added the comment:
Which version of Jython should I concentrate on to make these tests pass? The
2.5.4 release candidate, or the 2.7 beta?
--
nosy: +chrish42
___
Python tracker rep...@bugs.python.org
R. David Murray added the comment:
I'm guessing they've got a local fix in the release candidate and won't change
even their test code there, so I'd guess the beta. But the jython folks would
really be the ones to ask. Perhaps they will respond here (they are not at
pycon).
--
Christian Hudon added the comment:
I'll use Jython 2.7. The Jython people can backport the fix to 2.5.4, if they
want it there too.
So... this is marked as related to Python 3.2, but Jython is on Python 2 of
course. I'll just take the version as being wrong. So, what should the patch
that
R. David Murray added the comment:
Well, we want it to apply to python3 as well, since we want to see jython
support python3 eventually :)
Also, optparse is present in python3 for backward compatibility reasons
only...there were very few changes between the time python3 branched from
python2
Changes by Nilovna Bascunan-Vasquez cont...@nilovna.com:
--
nosy: +nilovna
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1704474
___
___
Éric Araujo mer...@netwok.org added the comment:
Hi Sandro. I think you may have closed too fast here: optparse is deprecated
in docs only, it’s not the recommendation anymore, but IIUC bugs should still
be fixed. A year and a half is sadly not a very long time for a Python bug,
time is
R. David Murray rdmur...@bitdance.com added the comment:
Making the tests pass on Jython is certainly worthwhile, if anyone wants to do
it. At a quick glance it looks like the optparse tests just need to be updated
and made a bit more lenient. Since Jython is lagging CPython by so much a fix
Sandro Tosi sandro.t...@gmail.com added the comment:
Hi, since optparse is now deprecated (in favor of argparse) and in a year and
half there was not progress on this, I'm closing this report.
--
nosy: +sandro.tosi
resolution: - wont fix
stage: - committed/rejected
status: open -
Mark Lawrence breamore...@yahoo.co.uk added the comment:
How do we find out which versions of optparse and test_optparse jython is
currently using?
--
nosy: +BreamoreBoy
versions: -Python 2.7
___
Python tracker rep...@bugs.python.org
Changes by Greg Ward g...@gerg.ca:
--
components: +Library (Lib) -Tests
title: test_optparse.py mod. for jython - optparse tests fail under Jython
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1704474
Philip Jenvey pjen...@users.sourceforge.net added the comment:
This looks like it was against Jython 2.2? Jython 2.5 passes 2.5's
test_optparse with only fixing __builtins__ and disabling the weakref test
So uses of __builtins__ should should be importing __builtin__ and use
that instead.
16 matches
Mail list logo
