× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That's interesting.  And on my machine in the livereload distribution folder (and to be specific, the python3.6/site-packages/livereload-2.6.3.dist-info folder) , I have a METADATA file which does indeed indicate that there is a tornado requirement.  But I'm uncertain whether METADATA is actually read at startup, or if it's just a generated document based on the code you've identified.

But I'm beginning to think we're circling in on the issue.


On 12/21/2020 4:35 PM, John Yeung wrote:
On Mon, Dec 21, 2020 at 4:16 PM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
Can any of the Python experts on the list here please tell me what this
means?

Specifically this:

File
"/QOpenSys/pkgs/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 860, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (tornado 6.1
(/QOpenSys/pkgs/lib/python3.6/site-packages),
Requirement.parse('tornado<6'), {'livereload'})

If I read this correctly, it looks like there is a requirement
definition somewhere specifying that I must have a tornado package whose
release is less than 6.
You are reading that correctly.

Now, I am not expert enough to really know the full picture, but I can
tell you a little more than you already know in this case.

There is a package called `livereload`. (I'm using backticks to
indicate literal characters.)

It is the package with that requirement. But the weird thing is that
it only requires `tornado` less than 6 when paired with Python 2.7!

See this file in the GitHub repo for `livereload` (you can probably
find the corresponding file somewhere in your `site-packages`):

https://github.com/lepture/python-livereload/blob/master/setup.py

And yes, I see all the error messages you quoted mention 3.6, but
somehow, *something* is thinking that you are trying to use 2.7. Maybe
some build step somewhere happened to use the `python` command in a
context where it was not the same as `python3`, and thus picked up the
Python 2.7 on your system. (We all have 2.7 on our system, even if we
didn't explicitly choose it, because for now, `yum` itself depends on
it!)

John Y.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.