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

Installation of only one component of the package #101

Open
Askaholic opened this issue Oct 9, 2020 · 5 comments · May be fixed by #177
Open

Installation of only one component of the package #101

Askaholic opened this issue Oct 9, 2020 · 5 comments · May be fixed by #177

Comments

@Askaholic
Copy link

I use only the database functionality of this package, and do all web management myself using aiohttp. It would be great if this package didn't pull requests into my dependency graph as my application is entirely async, (and also didn't force my aiohttp version to be less than 4 in case that ever gets updated).

I think you can use the extras_require argument to setup() (with setuptools) to add optional dependencies. Maybe something like:

extras_require={
    "all": ["requests>=2.24.0,<3.0.0", "aiohttp>=3.6.2,<4.0.0"],
    "requests": "requests>=2.24.0,<3.0.0",
    "aiohttp": "aiohttp>=3.6.2,<4.0.0",
}

For reference: https://setuptools.readthedocs.io/en/latest/userguide/dependency_management.html#id7
And example: https://github.com/palantir/python-language-server/blob/0fa74bae6fbb331498dbc39b6257d74357edea2f/setup.py#L51

Additionally, I see that urllib3 is listed in the requirements, but I don't see it being imported anywhere. Maybe that can be removed?

@sg3-141-592
Copy link

I noticed a similar issue when putting together an offline install of this package. I've also noticed the version of requests is very specific (June 2020 version and onwards), and can be loosened.

I've raised Pull Request #104 to

  • Remove urllib3
  • Make aiohttp and requests optional dependencies
  • Loosen the version of the requests library that can be used

I can understand if the maintainers don't want to make aiohttp and requests optional as it'll require anyone pulling this library in to do a different install command, and they might have issues with existing projects if they use this library as an unpinned dependency. I thought it was worth raising the Pull Request anyway, see what the feedback is like. I think the urllib and requests version change are worth including, even if adding the optional dependencies is too disruptive.

@menecio
Copy link

menecio commented Mar 8, 2021

In our case is exactly the opposite, but still the same principle. We have geoip2 as a dependency in our django projects but we aren't using asyncio at all, so having aiohttp as an optional requirement would be ideal.

@adi1
Copy link

adi1 commented Mar 16, 2022

Maxmind is retiring legacy databases on May 31 2022, forcing users to upgrade to GeoIP2 format. This means that all projects which are using only the offline database are now forced to install the unnecessary aiohttp client and its dependencies.

Is there any plan to make this dependency optional?

@oschwald
Copy link
Member

There is no immediate plans on doing this. As mentioned above, it may make sense to break this package into several packages at some point, but it is unlikely to happen soon.

If you are particularly concerned about unnecessary dependencies, I would suggest using maxminddb directly.

@adi1
Copy link

adi1 commented Mar 16, 2022

There is no immediate plans on doing this. As mentioned above, it may make sense to break this package into several packages at some point, but it is unlikely to happen soon.

If you are particularly concerned about unnecessary dependencies, I would suggest using maxminddb directly.

thanks for the db reader tip, this is exactly what I was looking for!

akx added a commit to akx/GeoIP2-python that referenced this issue Aug 27, 2024
akx added a commit to akx/GeoIP2-python that referenced this issue Aug 27, 2024
@akx akx linked a pull request Aug 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

5 participants