Skip to content
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

encoding scheme for class names #98

Closed

Conversation

fgeorgatos
Copy link
Collaborator

Hi,

see issue #86 in relation to this pull request.

nice weekend,
Fotis

Cedric Laczny [email protected] and others added 30 commits July 17, 2012 16:42
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Fotis Georgatos <[email protected]>
Signed-off-by: Cedric Laczny <[email protected]>
Signed-off-by: Cedric Laczny <[email protected]>
Signed-off-by: Cedric Laczny <[email protected]>
Signed-off-by: Cedric Laczny <[email protected]>
Signed-off-by: Cedric Laczny <[email protected]>
…, amos, idba, oases, pandaseq, velvet

Signed-off-by: Cedric Laczny <[email protected]>
# and can be extended freely as per ISO/IEC 10646:2012 / Unicode 6.1 names, as long as they are described in _CamelCase_ style:
# http://www.unicode.org/versions/Unicode6.1.0/
# So, yes, '_GreekSmallLetterEtaWithPsiliAndOxia_' *can* indeed be a fully valid package name; package "electron" in the original spelling anyone? ;-)
#
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use a multiple docstring here instead of comments, so we can have this function properly in Sphinx-generated documentation

@ghost ghost assigned boegel Aug 17, 2012
@boegel
Copy link
Member

boegel commented Aug 17, 2012

as discussed with @fgeorgatos , this pull request is closed because of the bunch of unrelated commits that were pulled along with it

@fgeorgatos will issue a new, cleaner, pull request, and will also document the encoding scheme implemented here as a part of the wiki documentations (describe encoding scheme we agreed on, and motivate the need to always use it, not just as a fallback in case of weird software names)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants