-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
removed references to deprecated python_utils file #417
base: develop
Are you sure you want to change the base?
Conversation
@athyrson06 Please follow the "getting started" instructions in the Oppia wiki https://github.com/oppia/oppia/wiki/Contributing-code-to-Oppia#setting-things-up -- we can't accept your PRs until you've done that. Once you've done that, feel free to reopen this PR if you like, and we can review it. I'm closing it for now so that it doesn't get merged accidentally. Thanks! |
I have now followed the steps, and I would like to request the pull request to be reopened. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @athyrson06! Just two comments, PTAL.
Custom-Pylint-checks.md
Outdated
print("Hello, world!") | ||
""") | ||
with open(filename, 'w') as tmp: | ||
tmp.write(""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deindent this and the following lines by 4.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
I did the necessary adjustments now. |
Changes Following #13935
In response to #13935, several misleading mentions and incorrect warnings were removed from the wiki. These included:
python_utils
mentions: The previous examples using onpython_utils.OBJECT
and other utility functions has been updated. I’ve replaced them with standard Python constructs and best practices.str
function: Some parts of the code were erroneously issuing warnings regarding the use of thestr()
function. This warning was removed asstr()
is the correct and accepted way to convert objects to strings in Python 3.Key Changes:
python_utils.OBJECT
in class definitions, replacing them with standard Python class definitions.str()
: The previous message warning against usingstr()
was incorrect, asstr()
is the appropriate way to convert to strings in Python 3.These updates help modernize the wiki, making it more in line with the new Oppia standard.