On Thu, Feb 12, 2015 at 11:58 AM, MRAB pyt...@mrabarnett.plus.com wrote:
On 2015-02-12 17:35, Ian Kelly wrote:
On Thu, Feb 12, 2015 at 10:19 AM, Skip Montanaro
skip.montan...@gmail.com wrote:
I believe this sort of lexicographical comparison wart is one of the
reasons
the Python-dev gang
On 12/02/2015 19:16, Ian Kelly wrote:
On Thu, Feb 12, 2015 at 11:58 AM, MRAB pyt...@mrabarnett.plus.com wrote:
On 2015-02-12 17:35, Ian Kelly wrote:
On Thu, Feb 12, 2015 at 10:19 AM, Skip Montanaro
skip.montan...@gmail.com wrote:
I believe this sort of lexicographical comparison wart is one
On 2015-02-12 17:35, Ian Kelly wrote:
On Thu, Feb 12, 2015 at 10:19 AM, Skip Montanaro
skip.montan...@gmail.com wrote:
I believe this sort of lexicographical comparison wart is one of the reasons
the Python-dev gang decided that there would be no micro versions 9. There
are too many similar
On 2015-02-12 12:16, Ian Kelly wrote:
It still becomes an issue when we get to Python 10.
Just call it Python X! :-)
Things break down again when we get to Python XIX.
'XVIII' 'XIX'
False
You know what this sub-thread gives me? The icks.
https://www.youtube.com/watch?v=6DzfPcSysAg
On 2/12/2015 11:16 AM, Ian Kelly wrote:
Things break down again when we get to Python XIX.
'XVIII' 'XIX'
False
Looks to me like you better check if your PEP313 patch is installed
properly. :)
Emile
--
https://mail.python.org/mailman/listinfo/python-list
On 2015-02-13 12:20, Ben Finney wrote:
Not sure why this is ridiculous.
Right, versions are effectively a special type [0], specifically
*because* they intentionally don't compare as scalar numbers or
strings. It's not “ridiculous” to need custom comparisons when
that's the case.
Python
Gisle Vanem gva...@yahoo.no writes:
That's exactly what they do now in IPython/utils/version.py with
the comment:
Utilities for version comparison
It is a bit ridiculous that we need these.
Not sure why this is ridiculous.
Right, versions are effectively a special type [0],
Skip Montanaro wrote:
I believe this sort of lexicographical comparison wart is one of the
reasons the Python-dev gang decided that there would be no micro versions
9. There are too many similar assumptions about version numbers out in
the real world.
Which is why there will be no Windows
'4.7': raise ImportError(IPython requires PyQt4 = 4.7, found
%s%QtCore.PYQT_VERSION_STR)
So even if '4.10' '4.7', my '4.10' is newer. What odd version
scheme is this really? I just edited that line to read:
if QtCore.PYQT_VERSION_STR '4.10':'
This looks like it's comparing them as strings
I believe this sort of lexicographical comparison wart is one of the
reasons the Python-dev gang decided that there would be no micro versions
9. There are too many similar assumptions about version numbers out in the
real world.
Skip
--
https://mail.python.org/mailman/listinfo/python-list
):
if QtCore.PYQT_VERSION_STR '4.7':
raise ImportError(IPython requires PyQt4 = 4.7, found
%s%QtCore.PYQT_VERSION_STR)
So even if '4.10' '4.7', my '4.10' is newer. What odd version scheme is
this really? I just edited that line to read:
if QtCore.PYQT_VERSION_STR '4.10':
Seems
'4.10' is newer. What odd version scheme is
this really? I just edited that line to read:
if QtCore.PYQT_VERSION_STR '4.10':
Looks to me like a fault in comparison format. Normally, you'd expect
that 4.10 follows 4.9 - that is, that the version number is a tuple of
integers
PyQt4 = 4.7, found
%s%QtCore.PYQT_VERSION_STR)
So even if '4.10' '4.7', my '4.10' is newer. What odd version scheme is
this really? I just edited that line to read:
if QtCore.PYQT_VERSION_STR '4.10':
Seems to be working fine now.
--
--gv
--
https://mail.python.org/mailman/listinfo/python-list
On Fri, Feb 13, 2015 at 4:19 AM, Skip Montanaro
skip.montan...@gmail.com wrote:
I believe this sort of lexicographical comparison wart is one of the reasons
the Python-dev gang decided that there would be no micro versions 9. There
are too many similar assumptions about version numbers out in
On Thu, Feb 12, 2015 at 10:19 AM, Skip Montanaro
skip.montan...@gmail.com wrote:
I believe this sort of lexicographical comparison wart is one of the reasons
the Python-dev gang decided that there would be no micro versions 9. There
are too many similar assumptions about version numbers out in
Tim Chase wrote: So the test should actually be something like
if LooseVersion(QtCore.PYQT_VERSION_STR) LooseVersion(4.10):
balk()
That's exactly what they do now in IPython/utils/version.py with
the comment:
Utilities for version comparison
It is a bit ridiculous that we need
On 2015-02-12 18:37, Gisle Vanem wrote:
Tim Chase wrote: So the test should actually be something like
if LooseVersion(QtCore.PYQT_VERSION_STR)
LooseVersion(4.10): balk()
That's exactly what they do now in IPython/utils/version.py with
the comment:
Utilities for version
17 matches
Mail list logo