Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

275
Views
Anaconda: any way to indicate if dependency issues prevent "conda update"ing the *absolute* latest version of a module?

I recently discovered my numpy installation (MacOS, with anaconda) was on an old version 1.11.x, instead of the latest 1.12.0, when a function documented on their website was not found. When I would type conda update numpy, I would be told the installation is up to date. Finally after trying to force conda install numpy=1.12.0, an error showed up indicating packages had dependency issues -- turns out my astropy installation (which I don't even use) required numpy version 1.11.x. After uninstalling astropy and installing numpy, the upgrade to version 1.12.0 was successful.

It really bothers me that anaconda did not give any sort of notice that it was ignoring the latest numpy version due to dependency issues. Is there any way to display, by force, some kind of warning or flag?

Edit: I see from this github issue thread that there seems to be no native way to do this, at the moment. Though perhaps until the developers add the feature, there is a slightly hacky way it can be done with a BASH script -- something like querying the latest version available, then conda installing and comparing the two version strings.

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

You are asking if it is possible to write code that will scan each line of environment.yml and report whether the "foo=X.Y.Z" version for foo is up-to-date, ignoring other deps in the file (like astropy) which might conflict and therefore hold it back.

Yes.

Write a script that iterates through each package line, tears down and then rebuilds a brand new environment with a one-line environment.yml (or even without that file), and installs the latest version in isolation. Read whatever version that turns out to be, compare against the target environment.yml, and report on any mismatches. If you write a script that you find useful, please do post it here.

over 4 years ago · Santiago Trujillo Report

0

I would actually say that using pip instead of conda would solve that problem as well. When upgrading a package using pip install --upgrade <package_name>, it will upgrade it to the latest version compatible with your OS and Python version. However, if this upgrade caused an installed package to no longer be compatible, pip will raise a warning telling you exactly that.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!