Skip to content

please include the PC/icons/* files from the python repository #945

Closed

Description

@doko42

please include the PC/icons/* files from the python repository. The python mercurial repository ships PC/icons/* files, although these are not used anymore for any Python build on any architecture. Please could you include these (maybe as part of community/python logs) in this project? The corresponding issue in the python tracker is http://bugs.python.org/issue17500

Activity

  1. berkerpeksag commented on Jun 6, 2016

    @berkerpeksag
    Member

    I think we already have the same logos (except the source.xar file) in the community logos page. If source.xar is an important file I can upload to the community logos page.

  2. malemburg commented on Jun 6, 2016

    @malemburg
    Member

    We do and the .xar file includes an old variant which is not the official version of the logo. Overall, the data in PC/icons/* dir is not official logo data, so I don't think we should include on the website.

    It may actually be better to do the reverse: i.e. add the official logo files from the website to the PC/logo/ dir and replace the in-official files with the official ones.

  3. malemburg commented on Jun 6, 2016

    @malemburg
    Member

    Some additional files are available here: https://wiki.python.org/psf/Python%20Logos

  4. ned-deily commented on Jun 6, 2016

    @ned-deily
    Member

    @doko42 brought this issue up with me at the PyCon sprints. His concern is that Debian considers .xar files to be non-free and thus they have to explicitly delete the file from each Python release when they repackage. It's not clear to us whether the .xar file is needed at all anymore but, as a precaution, he thought that saving in pythondotorg repo and removing it from cpython would make sure it didn't get lost and solve the non-free issue for redistributors. Otherwise, no other changes are being proposed.

  5. malemburg commented on Jun 6, 2016

    @malemburg
    Member

    On 06.06.2016 17:59, Ned Deily wrote:

    @doko42 brought this issue up with me at the PyCon sprints. His concern is that Debian considers .xar files to be non-free and thus they have to have explicitly delete the file from each Python release when they repackage. It's not clear to us whether the .xar file is needed at all anymore but, as a precaution, he thought that saving in pythondotorg repo and removing it from cpython would make sure it didn't get lost and solve the non-free issue for redistributors. Otherwise, no other changes are being proposed.

    Hi Ned,

    as mentioned, neither the .xar nor the .svg file in the directory
    contain the official logo files, so IMO they can both be deleted and
    don't have to be hosted anywhere else.

    If people are seeking the official logos, they should go to the
    website.

    Cheers,

    Marc-Andre Lemburg
    http://www.malemburg.com/

  6. ned-deily commented on Jun 7, 2016

    @ned-deily
    Member

    OK, good, then I guess we can close this issue. OK, @doko42?

  7. doko42 commented on Jun 10, 2016

    @doko42
    MemberAuthor

    ok. maybe a different request would be the addition of the logo with just the two snakes, which can be used as a desktop icon for starting the the interpreter.

  8. berkerpeksag commented on Jun 17, 2016

    @berkerpeksag
    Member

    Looks like this can be closed now. Please reopen if not.

  9. added a commit that references this issue on Jul 2, 2016
  10. added a commit that references this issue on Jul 20, 2016
  11. added a commit that references this issue on Sep 6, 2016
  12. 7 remaining items

  13. added a commit that references this issue on May 11, 2026
  14. added a commit that references this issue on May 14, 2026
  15. added a commit that references this issue on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions