Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg-hgtk thg-hgtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 515
    • Issues 515
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thg-hgtkthg-hgtk
  • Issues
  • #145

Closed
Open
Created Apr 04, 2009 by Bitbucket Importer@bitbucket_importerOwner

__version__.py from tar-ball

Created originally on Bitbucket by kiilerix (Mads Kiilerich)

When setup.py is run from a tar-ball (not a live hg repo with hg command available) then a default version.py will be created, and there is no way to specify what should go in it.

When the tar-ball is downloaded from http://bitbucket.org/tortoisehg/stable/get/tip.bz2 then there is no way setup.py can know what version it is. I suggest adding an option to setup.py, and its value should be used instead of running hg.

(The alternative is to overwrite the version.py created and installed by setup.py - that doesn't feel good.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking