Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
E
edx-platform
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
edx
edx-platform
Commits
af8cab2a
Commit
af8cab2a
authored
May 16, 2014
by
Calen Pennington
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix doc typos from #3746
parent
0e4f29a8
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
common/lib/opaque_keys/opaque_keys/__init__.py
+2
-2
No files found.
common/lib/opaque_keys/opaque_keys/__init__.py
View file @
af8cab2a
...
@@ -60,7 +60,7 @@ class OpaqueKey(object):
...
@@ -60,7 +60,7 @@ class OpaqueKey(object):
``CANONICAL_NAMESPACE``
``CANONICAL_NAMESPACE``
Identifies the key namespace for the particular key implementation
Identifies the key namespace for the particular key implementation
(when serializing). Key implementations must be registered using the
(when serializing). Key implementations must be registered using the
``CANONICAL_NAMESPACE``
i
s their entry_point name, but can also be registered
``CANONICAL_NAMESPACE``
a
s their entry_point name, but can also be registered
with other names for backwards compatibility.
with other names for backwards compatibility.
``KEY_FIELDS``
``KEY_FIELDS``
...
@@ -79,7 +79,7 @@ class OpaqueKey(object):
...
@@ -79,7 +79,7 @@ class OpaqueKey(object):
will already have been parsed.
will already have been parsed.
OpaqueKeys will not have optional constructor parameters (due to the implementation of
OpaqueKeys will not have optional constructor parameters (due to the implementation of
``KEY_FIELDS``), by default. However, an
d
implementation class can provide a default,
``KEY_FIELDS``), by default. However, an implementation class can provide a default,
as long as it passes that default to a call to ``super().__init__``.
as long as it passes that default to a call to ``super().__init__``.
:class:`OpaqueKey` objects are immutable.
:class:`OpaqueKey` objects are immutable.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment