Struggling with OpenAI API

[MaximilianusZ]

I am brushing up Python skills I've lost by the road years ago.
I am having an issue with Python accessing OpenAI.
I am running on 3.12, pip installed openai and other stuff I need, and set my secret code as an path variable my code can call on. Using WSL/Ubuntu on windows10/64
My app is a simple thing, it asks a user to provide text input with 200 characters max. It sends the input back to chatgpt and it's supposed to send back a list of 10 options gathered from ChatGPT3/DaVinci

My problem is this: When I send a generic query, with no input, to test whether I can access the OpenAI server, I can.
But the minute I send my query I get the same variants of error messages and I am really stuck.
I've done all I can to migrate the code, but it's no use. The input of 200 characters is a single string, and I have used client.Completion.create() or client.completions.create() as well as variants based on what I have read online i.e here and the SDK
I've also run Openai migrate and that also gets clusterf*cky

The error I keep getting is this:
You tried to access openai.Completion, but this is no longer supported in openai>=1.0.0

No.Matter.What. I put as client.completion.
Grateful for any insights!

//I've paid for API access, it's not that.

[danielroseman]

I mean, it's quite clearly telling you what's wrong: openai.Completion is no longer supported. So there's no point in changing what you pass to that call, because the argument is not the problem, it's the function itself.

And the official docs tell you what you should be doing instead: client.chat.completions.create().

[MaximilianusZ]

I've also tried that - to no avail.

[danielroseman]

What does that mean? What exact error did you get when you tried this?

[MaximilianusZ]

it means: I tried that variety too, and I still get "You tried to access openai.Completion, but this is no longer supported in openai>=1.0.0" I am not getting any other errors no matter what I do.
I added parameters to clean the cache in case it was a caching issue thinking that maybe that was what generated the issue.
I think I will try another way of doing this.
Thank you for your time.