Flexible Instance Naming in Class Methods.

[sboof911]

Change the hard code of self to the first argument passed in the methods.
Removing the condition on the first argument passed in a method of a class.

[pyccel-bot]

Hello again! Thank you for this new pull request 🤩.

Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:

• Write a clear PR description
• Add tests to check your code works as expected
• Update documentation if necessary
• Update Changelog
• Ensure any relevant issues are linked
• Ensure new tests are passing

[sboof911]

/bot tests

[pyccel-bot]

This bot reacts to all comments which begin with /bot. This phrase can be followed by any of these commands:

• show tests : Lists the tests which can be triggered
• run X : Triggers the test X (acceptable values for X can be seen using show tests). Multiple tests can be specified separated by spaces.
• try V X : Triggers the test X (acceptable values for X can be seen using show tests) using Python version V. Multiple tests can be specified separated by spaces, but all will use the same Python version.
• mark as ready : Runs the PR tests. If they pass then it adds the appropriate review flag and requests reviews. This command should be used when the PR is first ready for review, or when a review has been answered.
• commands : Shows this list detailing all the commands which are understood.
• trust user X : Tells the bot that a new user X is trusted to run workflows (prevents misuse of GitHub actions for mining etc). This command can only be used by a trusted reviewer.
• accept coverage : Tells the bot that the coverage errors have been investigated and cannot be fixed in this PR.

Beware: if you have never contributed to this repository and you are not a member of the Pyccel organisation, the bot will ignore all requests to run tests until permitted by a trusted reviewer.

[sboof911]

/bot show tests

[pyccel-bot]

The following is a list of keywords which can be used to run tests. Tests in bold are run by pull requests when they are marked as ready for review or pushed to while not in draft:

• linux : Runs the unit tests on a Linux system.
• windows : Runs the unit tests on a Windows system.
• macosx : Runs the unit tests on a MacOS X system.
• coverage : Runs the unit tests on a Linux system and checks the coverage of the tests.
• docs : Checks if the documentation follows the numpydoc format.
• pylint : Runs pylint on files which are too big to be handled by codacy.
• pyccel_lint : Runs a linter to check that Pyccel's best practices are followed.
• spelling : Checks if everything in the documentation is spelled (and capitalised) correctly.
• pr_tests : Runs all the tests marked in bold.
• pickle : Checks that .pyccel files have been correctly generated and installed by the installation process.
• editable_pickle : Checks that .pyccel files have been correctly generated and installed by the editable installation process.
• pickle_wheel : Checks that .pyccel files have been correctly generated and packaged into the wheel.
• linux_anaconda : Runs the unit tests on a linux system using anaconda for python.
• windows_anaconda : Runs the unit tests on a windows system using anaconda for python.

These tests can be run with the command /bot run X (multiple tests can be specified separated by spaces), or with try V X to test on Python version V.

[sboof911]

/bot run coverage docs pylint pyccel_lint spelling

[pyccel-bot]

Good job ! Your PR is using all the code it added/changed.

[sboof911]

/bot run pyccel_lint

[sboof911]

/bot run docs pylint spelling

[sboof911]

/bot run pr_tests

[sboof911]

/bot run pr_tests

[pyccel-bot]

Good job ! Your PR is using all the code it added/changed.

[yguclu]

@sboof911 Is this PR ready for review?