Issue Setting up a cache

[dsambrano]

The API works great!!! Unfortunately while setting up caching, I consistently get this error:

File "C:\Users\{USER}\anaconda3\envs\apps\lib\site-packages\beckett\clients.py", line 194, in __init__
    super(BaseClient, self).__init__(*args, **kwargs)
TypeError: object.__init__() takes exactly one argument (the instance to initialize) 

I am running python: 3.8.12 on a windows 10 machine, with Pokepy version 0.4.

Another small issue is for whatever reason everytime I get a return from the client it is in a list instead of the pokepy resource class (as shown in the documentation). Any ideas?

[Kronopt]

Hey @dsambrano,

latest version of pokepy is 0.6.2. Try using the latest version and see if your issues are addressed

[dsambrano]

Thanks you the advice. Unfortunately, I get a Resolution Error when trying to pip install that specific version (or anything about .0.6 for that matter) via pip install pokepy==0.6.2

Namely because the beckett 0.8 dependency requires verions 2.10.0 of requests and pokepy (0.6.2) requires version 2.21 of requests. I have the most updated version of pip and I believe am using the most recent version of python the module supports (3.8.12) but could be wrong about that.

ERROR: Cannot install beckett==0.8.0 and pokepy==0.6.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    pokepy 0.6.2 depends on requests==2.21.*
    beckett 0.8.0 depends on requests==2.10.0

[Kronopt]

Damn... this wasn't a problem some versions of pip ago...
Well, I guess pokepy is broken until I can manage to deprecate beckett...

You could checkout pokebase

[Naramsim]

Maybe @Kronopt you could just submit a PR over at beckett updating the requirements.

[Kronopt]

I could, but It would probably just go unmerged.
Phalt has already mentioned that he is no longer working on beckett, so I'd rather not propose any new changes

[Naramsim]

One could fork it, update the deps and push a new package. I can do it, or you can do it (if you feel maintaining the new package).

[Kronopt]

I don't feel like maintaining that new package as I'm already working on another one to replace it.
Feel free to do it if you want to, though

[GunnerStone]

Did this ever get fixed? Still running into same issue

[Kronopt]

Not yet

[Glowing0v3rlord]

Has this been fixed yet?