refactor: change methods not using its bound instance to staticmethods

[deepsource-autofix]

The method doesn't use its bound instance. Decorate this method with @staticmethod decorator, so that Python does not have to instantiate a bound method for every instance of this class thereby saving memory and computation. Read more about staticmethods here.

Summary by Sourcery

Enhancements:

• Declare methods that do not use the bound instance as static methods to improve efficiency.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request refactors methods that do not use their bound instance by decorating them with the @staticmethod decorator. This change improves memory and computational efficiency by preventing Python from instantiating a bound method for each class instance.

Class diagram showing staticmethod changes in classifier and generator

classDiagram
    class Classifier {
        -model
        +_split_data(path: Path)
        +show_score()
        +_tokenize()$ 
        +train()$ 
        +test()$ 
        +predict()$ 
    }
    note for Classifier "Methods marked with $ are now static"

    class Generator {
        -model
        -tokenizer
        +__init__(config: dict, format: Callable)
        +_openai_generate(input: str, base_url: str, model_name: str, api_key: str)$ 
    }
    note for Generator "Methods marked with $ are now static"

Loading

File-Level Changes

Change	Details	Files
Methods not using bound instances are converted to static methods using the @staticmethod decorator.	The methods _tokenize, train, test, and predict in the classfy.py file are converted to static methods. This refactoring prevents unnecessary bound method instantiation, improving memory and computational efficiency.	src/everyai/classfier/classfy.py
The _openai_generate method is converted to a static method.	The _openai_generate method in the generate.py file is converted to a static method using the @staticmethod decorator. This refactoring prevents unnecessary bound method instantiation, improving memory and computational efficiency.	src/everyai/generator/generate.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, deepsource-autofix[bot]!). We assume it knows what it's doing!

[deepsource-io]

Here's the code health analysis summary for commits d60e0a2..1b180ad. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	❌ Failure	❗ 7 occurences introduced 🎯 10 occurences resolved	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.