Scikits version system
Folks, I'm trying to add some version number to our package (timeseries), following the example in http://scipy.org/scipy/scikits/wiki/ScikitsForDevelopers However, something must be going wrong, as the only __version__ number I get is 0.5, no matter the version number I try to set. Could anybody help me ? This is really becoming frustrating by the hour. Thanks a lot in advance P.
On Mon, Jun 16, 2008 at 20:18, Pierre GM <pgmdevlist@gmail.com> wrote:
Folks, I'm trying to add some version number to our package (timeseries), following the example in http://scipy.org/scipy/scikits/wiki/ScikitsForDevelopers However, something must be going wrong, as the only __version__ number I get is 0.5, no matter the version number I try to set.
Do you have an old egg or .egg-info directory lying around? -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Mon, Jun 16, 2008 at 20:18, Pierre GM <pgmdevlist@gmail.com> wrote:
Folks, I'm trying to add some version number to our package (timeseries), following the example in http://scipy.org/scipy/scikits/wiki/ScikitsForDevelopers However, something must be going wrong, as the only __version__ number I get is 0.5, no matter the version number I try to set.
Well, the current trunk doesn't build into an egg for me: you have tag_svn_revision set to an invalid value in setup.cfg. You also have the name of the package wrong in the setup() call, so it makes and egg called "timeseries" rather than "scikits.timeseries" which is what it should be. Fixing these, and uncommenting out the implementation of the scheme described on the wiki works for me. Attached is the patch against SVN trunk. In doing this, I found a few places where there are mixed line endings. Please take a look at normalizing these. Also please go through the commented-out blocks of obsolete code and delete any of it that you can. SVN remembers so the file doesn't have to. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
Robert, First of all, thanks an awful lot again for your help. On Monday 16 June 2008 21:40:44 Robert Kern wrote:
Well, the current trunk doesn't build into an egg for me: you have tag_svn_revision set to an invalid value in setup.cfg. You also have the name of the package wrong in the setup() call, so it makes and egg called "timeseries" rather than "scikits.timeseries" which is what it should be. Fixing these, and uncommenting out the implementation of the scheme described on the wiki works for me.
I had figured that the 1 was in fact a truth value, but thanks for pointing out the error in the base setup.py.
In doing this, I found a few places where there are mixed line endings. Please take a look at normalizing these.
Mmh, I'm not sure what you mean about the line endings...
Also please go through the commented-out blocks of obsolete code and delete any of it that you can. SVN remembers so the file doesn't have to.
You're quite right, sorry about that. After getting rid of rotten eggs and performing a clean install, I get the proper results, at last. Thanks again !
On Mon, Jun 16, 2008 at 21:46, Pierre GM <pgmdevlist@gmail.com> wrote:
On Monday 16 June 2008 21:40:44 Robert Kern wrote:
In doing this, I found a few places where there are mixed line endings. Please take a look at normalizing these.
Mmh, I'm not sure what you mean about the line endings...
For example, scikits/timeseries/__init__.py. The non-empty lines end in \r\n; the blank lines end in \n. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Monday 16 June 2008 23:20:03 Robert Kern wrote:
On Mon, Jun 16, 2008 at 21:46, Pierre GM <pgmdevlist@gmail.com> wrote:
On Monday 16 June 2008 21:40:44 Robert Kern wrote:
In doing this, I found a few places where there are mixed line endings. Please take a look at normalizing these.
Mmh, I'm not sure what you mean about the line endings...
For example, scikits/timeseries/__init__.py. The non-empty lines end in \r\n; the blank lines end in \n.
Ah OK, indeed. Guess we'll have to decide of a format with Matt. Thanks again.
participants (2)
-
Pierre GM
-
Robert Kern