Updated duckduckgo-search. (Fixes #490)

[CameronJGrant]

I've updated everything to the latest versions and added poetry as a dependency management system. Note that later versions of "duckduckgo-search" need to use "curl-cffi" and that brought about a host of new issues that needed to be dealt with. That's why there are a so many edits to the Dockerfile.

[Jipok]

Why remove requirements.txt?

[CameronJGrant]

It hasn't been removed. It's been replaced with the "pyproject.toml" file (Poetry https://python-poetry.org/).

It works the same except it ensures package versions work together. It also generates a lock file, with hashes for each package, so that your environment is identical to everyone elses. This is especially important when building Dockerfiles. Otherwise we can have a situation where "chatgpt-telegram-bot" works on your system, but not on mine.

If you're not familiar with it, check it out. It will help with future projects.

[Jipok]

It hasn't been removed.

It was clearly deleted judging by what Github shows.

It works the same except...

except that it requires installing poetry. In which I don’t see any point at all for such projects.
From my point of view, you are adding an additional dependency that needs to be installed on the system in order to have a slightly more convenient way of describing dependencies. I really don’t like this kind of stuff, it’s overcomplicated. I don't understand why you're bringing Docker into this at all.

[k3it]

@Jipok has a point. it looks like poetry repo has 612 open issues and 85 pull requests, so it's a highly complex dependency all by itself.

[CameronJGrant]

I've editted this response.

I agree with both of your points. This should have been maybe 3 separate PR's. One for the fix. One for the overall updates. And one for the dependency manager. I'll edit this PR when I have time. Otherwise we can take @Jipok's PR and add a Dockerfile fix to it and it will be fine too.

[CameronJGrant]

I've made this simpler now. No more Poetry.

[k3it]

quick tested and the build works with the #501 (#504 also), looks good to me. thank you!

[k3it]

paging @n3d1117

[tobias-strenger]

For me, this literally doubled the image size. Ie Dive shows a lot in /usr/lib/. I don't know exactly how to selectively remove the build dependencies.

[CameronJGrant]

For me, this literally doubled the image size. Ie Dive shows a lot in /usr/lib/. I don't know exactly how to selectively remove the build dependencies.

Hmm. I did remove the gcc build dependencies in the line RUN apk del build-base. There shouldn't be any other build dependencies. The "curl-impersonate" libraries are copied from a separate image so I don't build them.

It may be a moot point anyway as I've heard nothing from @n3d1117.

[A1RWALK3R]

For now it is

duckduckgo_search~=5.0
curl-cffi~=0.6.3b1

[n3d1117]

Hi all, sorry for the long wait, are these changes still relevant? Or is it enough to update to latest duckduckgo_search and curl-cffi like @A1RWALK3R suggested?

[CameronJGrant]

Thanks to @yifeikong for his update of curl_cffi @A1RWALK3R suggestion should do it.

[chk86]

This fix no longer works. DDG is returning "Failed to get response...202 Ratelimit".

[chk86]

And by this fix I mean @A1RWALK3R 's suggestion.

[A1RWALK3R]

@chk86 I think you can try duckduckgo_search==5.3.0b4

I haven't checked it yet, but I found useful information about 202 Ratelimit here

[chk86]

Thanks, @A1RWALK3R . I saw that actually, that fix doesn't work, either. I tried recreating the bot with that version. I'll just be patient till they get it sorted.