griefith/test
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Cleanup: Grammar: Fix uses of "for e.g."

Browse Source 
e.g. stands for "exempli gratia" in Latin which means "for example".
The best way to make sure it makes sense when writing is to just expand
it to "for example". In these cases where the text was "for e.g.", that
leaves us with "for for example" which makes no sense. This commit fixes
all 110 cases, mostly just just replacing the words with "for example",
but also restructuring the text a bit more in a few cases, mostly by
moving "e.g." to the beginning of a list in parentheses.

Pull Request: https://projects.blender.org/blender/blender/pulls/139596
This commit is contained in:
Hans Goudey
2025-05-29 21:21:18 +02:00
committed by Hans Goudey
parent 5747f839e8
commit 91803e130f
74 changed files with 116 additions and 114 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
scripts/addons_core/bl_pkg/bl_extension_notify.py
View File

@@ -162,7 +162,7 @@ def sync_apply_locked(repos_notify, repos_notify_files, unique_ext):
except Exception as ex:
sys.stderr.write("Failed to remove file before renaming: {:s}\n".format(str(ex)))
continue
# Not expected to fail, in the case it might (corrupt file-system for e.g.),
# Not expected to fail, in the case it might (corrupt file-system for example),
# the script should continue executing.
try:
os.rename(filepath, filepath_dst)
@@ -585,7 +585,7 @@ def update_non_blocking(*, repos_fn, immediate=False):
# Perform a non-blocking update on ``repos``.
# Updates are queued in case some are already running.
# `repos_fn` A generator or function that returns a list of ``(RepoItem, do_online_sync)`` pairs.
# Some repositories don't check for update on startup for e.g.
# Some repositories don't check for update on startup for example
# Needed so `update_in_progress` doesn't get confused by an old completed item hanging around.
# Further, there is no need to keep this item any longer than is needed if a new notification is added.

6
scripts/addons_core/bl_pkg/bl_extension_ui.py
View File

@@ -143,7 +143,7 @@ def pkg_manifest_zip_all_items(pkg_manifest_local, pkg_manifest_remote):
# While this is not a strict definition (internally they're just add-ons from different places),
# for the purposes of the UI it makes sense to differentiate add-ons this way because these add-on
# characteristics are mutually exclusive (there is no such thing as a user-core-extension for e.g.).
# characteristics are mutually exclusive (there is no such thing as a user-core-extension for example).
# Add-On Types:
@@ -1546,7 +1546,7 @@ def extensions_panel_draw_impl(
# Exceptions to this rule:
# - *version*: when outdated, it's useful to show both versions as the user may wish to upgrade.
# Otherwise it's typically not useful to attempt to make the user aware of other minor discrepancies.
# (changes to the description or maintainer for e.g.).
# (changes to the description or maintainer for example).
#
# - *website*: the host of the remote repository may wish to override the website with a landing page for
# each extension, this page can show information managed by the organization hosting repository,
@@ -1997,7 +1997,7 @@ def extensions_panel_draw(panel, context):
# When an update is in progress disallow any destructive operations.
# While a non-blocking update is nice, users should *never* be performing
# destructive operations with an outdated repository. There are a couple of reasons for this.
# - Pressing "Install" on an extension may either fail (the version may be old for e.g.).
# - Pressing "Install" on an extension may either fail (the version may be old for example).
# - Pressing any buttons immediately before the UI refreshes risks the user installing or operating
# on the wrong extension, one which they may not trust!
# Prevent these kinds of accidents by disabling parts of the extension UI while synchronize is in progress.

6
scripts/addons_core/bl_pkg/cli/blender_ext.py
View File

@@ -2320,7 +2320,7 @@ def python_versions_from_wheel(wheel_filename: str) -> set[tuple[int] | tuple[in
abi_tag = wheel_filename_split[-2]
# NOTE(@ideasman42): when the ABI is set, simply return the major version,
# This is needed because older version of CPython (3.6) for e.g. are compatible with newer versions of CPython,
# This is needed because older version of CPython (3.6) for example are compatible with newer versions of CPython,
# but returning the old version causes it not to register as being compatible.
# So return the ABI version to allow any version of CPython 3.x.
#
@@ -2835,7 +2835,7 @@ def pkg_manifest_detect_duplicates(
del python_versions_full
# This can be expanded with additional values as needed.
# We could in principle have ABI flags (debug/release) for e.g.
# We could in principle have ABI flags (debug/release) for example
PkgCfgKey = tuple[
# Platform.
str,
@@ -4870,7 +4870,7 @@ class subcmd_author:
*,
manifest: PkgManifest,
# NOTE: This path is only for inclusion in the error message,
# the path may not exist on the file-system (it may refer to a path inside an archive for e.g.).
# the path may not exist on the file-system (it may refer to a path inside an archive for example).
pkg_manifest_filepath: str,
valid_tags_filepath: str,
) -> bool:

2
scripts/addons_core/bl_pkg/tests/test_cli_blender.py
View File

@@ -984,7 +984,7 @@ class TestPythonVersions(TestWithTempBlenderUser_MixIn, unittest.TestCase):
self.repo_add(repo_id=repo_id, repo_name=repo_name)
this_python_version_major, this_python_version_minor = sys.version_info[:2]
# TODO: this test doesn't make sense for the first Python major releases (4.0 for e.g.).
# TODO: this test doesn't make sense for the first Python major releases (4.0 for example).
if this_python_version_minor == 0:
return

2
scripts/modules/_bpy_internal/extensions/stale_file_manager.py
View File

@@ -162,7 +162,7 @@ class StaleFiles:
#
# If this ever did happen besides potentially trying to remove `base_directory`,
# this path could be treated as a file which could not be removed and queued for
# removal again causing a single space (for e.g.) to be left in the stale file,
# removal again causing a single space (for example) to be left in the stale file,
# trying to be removed every startup and failing.
# Avoid all these issues by checking the path doesn't resolve to being the same path as it's parent.
is_same = False

2
scripts/modules/_bpy_internal/extensions/wheel_manager.py
View File

@@ -464,7 +464,7 @@ def wheel_version_from_filename_for_cmp(
so comparing the first 3 numbers is sufficient. The trailing string is just a tie breaker in the
unlikely event it differs.
If supporting the full spec, comparing: "1.1.dev6" with "1.1.6rc6" for e.g.
If supporting the full spec, comparing: "1.1.dev6" with "1.1.6rc6" for example
we could support this doesn't seem especially important as extensions should use major releases.
"""
filename_split = filename.split("-")

2
scripts/modules/addon_utils.py
View File

@@ -1119,7 +1119,7 @@ def _initialize_extensions_compat_ensure_up_to_date(extensions_directory, extens
if cache_data is not None:
# NOTE: the exception handling here is fairly paranoid and accounts for invalid values in the loaded cache.
# An example would be values expected to be lists/dictionaries being other types (None or strings for e.g.).
# An example would be values expected to be lists/dictionaries being other types (None or strings for example).
# While this should not happen, some bad value should not prevent Blender from loading properly,
# so report the error and regenerate cache.
try:

2
scripts/modules/rna_info.py
View File

@@ -711,7 +711,7 @@ def BuildRNAInfo():
print("rna_info.BuildRNAInfo(..): ignoring type", repr(rna_type_name))
# Now, there are some sub-classes in add-ons we also want to include.
# Cycles for e.g. these are referenced from the Scene, but not part of
# Cycles for example. These are referenced from the Scene, but not part of
# bpy.types module.
# Include all sub-classes we didn't already get from 'bpy.types'.
i = 0

2
scripts/modules/rna_xml.py
View File

@@ -239,7 +239,7 @@ def rna2xml(
# paths "escaping" the intended data types, potentially writing into unexpected settings.
# This is done because the XML itself defines the attributes which are recursed into,
# there is a possibility the XML recurse into data that isn't logically owned by "root",
# out of the theme and into user preferences for e.g. which could change trust settings
# out of the theme and into user preferences for example, which could change trust settings
# even executing code.
#
# At the time of writing it seems this is not possible with themes (the main user of this functionality),

4
scripts/presets/keyconfig/keymap_data/blender_default.py
View File

@@ -96,7 +96,7 @@ class Params:
#
# NOTE: This is typically used for active tool key-map items however it should never
# be used for selection tools (the default box-select tool for example).
# Since this means with RMB select enabled in edit-mode for e.g.
# Since this means with RMB select enabled in edit-mode for example
# `Ctrl-LMB` would be caught by box-select instead of add/extrude.
"tool_maybe_tweak_event",
)
@@ -603,7 +603,7 @@ def _template_items_tool_select(
if params.select_mouse == 'LEFTMOUSE':
# Use 'PRESS' for immediate select without delay.
# Tools that allow dragging anywhere should _NOT_ enable the fallback tool
# unless it is expected that the tool should operate on the selection (click-drag to rip for e.g.).
# unless it is expected that the tool should operate on the selection (click-drag to rip for example).
return [
(operator, {"type": 'LEFTMOUSE', "value": 'PRESS'},
{"properties": [

6
scripts/startup/bl_operators/wm.py
View File

@@ -56,7 +56,7 @@ def _rna_path_prop_search_for_context_impl(context, edit_text, unique_attrs):
def rna_path_prop_search_for_context(self, context, edit_text):
# NOTE(@campbellbarton): Limiting data-path expansion is rather arbitrary.
# It's possible for e.g. that someone would want to set a shortcut in the preferences or
# It's possible for example that someone would want to set a shortcut in the preferences or
# in other region types than those currently expanded. Unless there is a reasonable likelihood
# users might expand these space-type/region-type combinations - exclude them from this search.
# After all, this list is mainly intended as a hint, users are not prevented from constructing
@@ -69,7 +69,7 @@ def rna_path_prop_search_for_context(self, context, edit_text):
if area.type == 'PREFERENCES':
continue
# Ignore the same region type multiple times in an area.
# Prevents the 3D-viewport quad-view from attempting to expand 3 extra times for e.g.
# Prevents the 3D-viewport quad-view from attempting to expand 3 extra times for example
region_type_unique = set()
for region in area.regions:
if region.type not in {'WINDOW', 'PREVIEW'}:
@@ -3503,7 +3503,7 @@ class WM_MT_region_toggle_pie(Menu):
bl_label = "Region Toggle"
# Map the `region.type` to the `space_data` attribute & text label.
# The order of items defines priority, so in the sequencer for e.g.
# The order of items defines priority, so for example in the sequencer
# when there is both a toolbar and channels, the toolbar gets the
# axis-aligned pie, and the channels don't.
_region_info = {