Skip to content

Conversation

@qwcode
Copy link
Contributor

@qwcode qwcode commented Oct 29, 2014

based on the consensus I perceived in #106 (at least between 3 people) to go back to using "package" (not "distribution" or "distribution package")

note that I added an opening paragraph to the installation tutorial explaining the ambiguity.

the glossary stayed as it is with the "Meaning #1/#2"" distinction for "Package"

Copy link
Member

Choose a reason for hiding this comment

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

Meaning #1?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh yes, #1

@ncoghlan
Copy link
Member

One cross reference that doesn't look right, one minor suggested tweak.

In reviewing this, I also noticed that the glossary entry for package meaning number 1 is slightly outdated - it doesn't account for the native namespace package import support added in Python 3.3 (which does away with the need for init.py files).

Also related: even if we don't use them elsewhere yet, perhaps it would be worth mentioning the optional "import package" and "distribution package" qualifiers in their respective glossary entries?

@qwcode
Copy link
Contributor Author

qwcode commented Oct 29, 2014

worth mentioning the optional "import package" and "distribution package" qualifiers

ok, let me try to work them into the glossary.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants