Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove ete3 dependency #4956

Merged
merged 1 commit into from
May 25, 2021
Merged

remove ete3 dependency #4956

merged 1 commit into from
May 25, 2021

Conversation

ltalirz
Copy link
Member

@ltalirz ltalirz commented May 20, 2021

It seems the last use of ete3 was removed in commit
287d138 but the dependency was not
removed.

It seems the last use of ete3 was removed in commit
287d138 but the dependency was not
removed.
@ltalirz
Copy link
Member Author

ltalirz commented May 20, 2021

mentioning @aiidateam/dependency-manager

@codecov
Copy link

codecov bot commented May 20, 2021

Codecov Report

Merging #4956 (b817d2f) into develop (2f1c1f8) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #4956   +/-   ##
========================================
  Coverage    80.05%   80.05%           
========================================
  Files          515      515           
  Lines        36611    36611           
========================================
  Hits         29305    29305           
  Misses        7306     7306           
Flag Coverage Δ
django 74.50% <ø> (ø)
sqlalchemy 73.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2f1c1f8...b817d2f. Read the comment docs.

@ltalirz ltalirz requested a review from sphuber May 20, 2021 17:40
@sphuber
Copy link
Contributor

sphuber commented May 21, 2021

How did you discover this? If you haven't done so already, would it make sense to do a quick scan for other unused dependencies?

@ltalirz
Copy link
Member Author

ltalirz commented May 21, 2021

Sure, we can have a look:

pipreqs

$ pip install pipreqs
...
$ pipreqs --print --no-pin aiida | tr '[:upper:]' '[:lower:]' | sort
INFO: Successfully output requirements
aio_pika
aldjemy
alembic
archive_path
ase
beautifulsoup4
bpython
circus
click
click_completion
click_config_file
click_spinner
contextvars
dataclasses
disk_objectstore
docutils
flask
flask_cors
flask_restful
graphviz
ipython
jinja2
jsonschema
kiwipy
matplotlib
mayavi
numpy
pamqp
paramiko
pgsu
pgtest
phonopy
plumpy
psutil
psycopg2
psycopg2_binary
pymatgen
pymysql
pyparsing
pytest
python_dateutil
pytz
pyyaml
pyzmq
reentry
requests
scipy
simplejson
singledispatch
spglib
sphinx
sphinxcontrib_programoutput
sqlalchemy_utils
tabulate
tqdm
tzlocal
upf_to_json
werkzeug
wrapt

This misses the django and sqlalchemy imports; likely because we have folders named django and sqlalchemy in aiida.orm.implementation.

I've checked the rest from the setup.json against this list and could not find any other unused package.

conda_forge_tick

You may have noticed that the conda-forge bot does exactly this analysis (see e.g. the "Packages found in the meta.yaml but not found by inspection" here ), which is why I'm quite confident that this was not a problem with any recent AiiDA releases.
I think the commit 287d138 where deprecated functionality was removed is the most likely place for overlooking something like this.

The bot is using this bit of code.
I haven't installed & run it myself - you're welcome to do so if you like. Otherwise we'll know after the next release ;-)

Copy link
Contributor

@sphuber sphuber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ltalirz

@sphuber sphuber merged commit 3055897 into aiidateam:develop May 25, 2021
@sphuber sphuber deleted the remove-ete3 branch May 25, 2021 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants