Modify

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#842 closed defect (invalid)

bdist_egg does not work with python-2.5

Reported by: ThurnerRupert Owned by: mgood
Priority: high Component: AccountManagerPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10

Description

when trying to upgrade to python-2.5 we experienced the following error:

running bdist_egg
Traceback (most recent call last):
  File "./setup.py", line 36, in <module>
    test_suite = 'acct_mgr.tests.suite',
  File "/local/lib/python2.5/distutils/core.py", line 151, in setup
    dist.run_commands()
  File "/local/lib/python2.5/distutils/dist.py", line 974, in run_commands
    self.run_command(cmd)
  File "/local/lib/python2.5/distutils/dist.py", line 993, in run_command
    cmd_obj.ensure_finalized()
  File "/local/lib/python2.5/distutils/cmd.py", line 117, in ensure_finalized
    self.finalize_options()
  File "/local/lib/python2.5/site-packages/setuptools-0.6c3-py2.5.egg/setuptools/command/bdist_egg.py", line 94, in finalize_options
  File "/local/lib/python2.5/distutils/cmd.py", line 319, in get_finalized_command
    cmd_obj.ensure_finalized()
  File "/local/lib/python2.5/distutils/cmd.py", line 117, in ensure_finalized
    self.finalize_options()
  File "/local/lib/python2.5/site-packages/setuptools-0.6c3-py2.5.egg/setuptools/command/egg_info.py", line 85, in finalize_options
  File "/local/lib/python2.5/site-packages/setuptools-0.6c3-py2.5.egg/setuptools/command/egg_info.py", line 179, in tags
  File "/local/lib/python2.5/site-packages/setuptools-0.6c3-py2.5.egg/setuptools/command/egg_info.py", line 224, in get_svn_revision
ValueError: invalid literal for int() with base 10: ''

Attachments (0)

Change History (8)

comment:1 Changed 8 years ago by coderanger

Sounds like you aren't using a checkout to do the build. Try removing the setup.cfg file.

comment:2 Changed 8 years ago by ThurnerRupert

  • Resolution set to invalid
  • Status changed from new to closed

yes, this was it, removed it and it worked. but the automatic build script does a clean before, and this leaves setup.cfg. is there any clean command removing the setup.cfg too?

comment:3 follow-up: Changed 8 years ago by coderanger

Setuptools should probably handle that situation a bit more gracefully. It always assumes that if the build should be tagged with a revision number, that the build must be taking place in a subversion working copy.

comment:4 in reply to: ↑ 3 Changed 8 years ago by mgood

Replying to coderanger:

Setuptools should probably handle that situation a bit more gracefully. It always assumes that if the build should be tagged with a revision number, that the build must be taking place in a subversion working copy.

Well, I tested it here with an exported version of the code (not a working copy) and it was fine. I tried the setuptools 0.7dev and downgraded to 0.6c3 as well and both seemed OK. The version was simply "0.1.2dev" with no SVN revision #. You can report the issue on the Distutils-SIG mailing list to see if PJE knows what's going on.

comment:5 follow-up: Changed 8 years ago by anonymous

this plugin is the only one having the setup.cfg file in the subversion repository, see #863.

comment:6 in reply to: ↑ 5 ; follow-up: Changed 8 years ago by mgood

Replying to anonymous:

this plugin is the only one having the setup.cfg file in the subversion repository, see #863.

No, "official" plugins such as the t:SpamFilter and t:WebAdmin both include the setup.cfg file.

comment:7 in reply to: ↑ 6 ; follow-up: Changed 8 years ago by anonymous

Replying to mgood:

Replying to anonymous:

this plugin is the only one having the setup.cfg file in the subversion repository, see #863.

No, "official" plugins such as the t:SpamFilter and t:WebAdmin both include the setup.cfg file.

why are they doing so, and the others not? if removing it makes it build clean?

comment:8 in reply to: ↑ 7 Changed 8 years ago by mgood

Replying to anonymous:

why are they doing so, and the others not? if removing it makes it build clean?

I assume the other developers just don't know about setup.cfg. They should probably include it too so that their development builds are tagged as such.

Removing the file is simply a workaround to the real issue, which is with the user's ".svn/entries" file as I described in #863. This file is either corrupt or in a format not recognized by setuptools at this time. Someone experiencing this problem will need to report the issue to the Distutils mailing list with information from the ".svn/entries" file in order to debug the problem and get it fixed in setuptools if necessary.

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from mgood. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.