Hi,
2011/10/24 Nathan Jones :
>> migrate.versioning.exceptions.ScriptError: You can only have one
>> Python script per version, but you have:
>> /usr/lib/python2.7/site-packages/pytrainer/upgrade/versions/011_populate_lap_details.py
>> and
>> /usr/lib/python2.7/site-packages/pytrainer/upgrade/ver
> migrate.versioning.exceptions.ScriptError: You can only have one
> Python script per version, but you have:
> /usr/lib/python2.7/site-packages/pytrainer/upgrade/versions/011_populate_lap_details.py
> and
> /usr/lib/python2.7/site-packages/pytrainer/upgrade/versions/011_remove_db_version.py
> $
Hi,
2011/10/23 Nathan Jones :
> Thanks guys for the sample data files. I have now verified the upgrade
> to version 1.9.0 works from 1.7.1, 1.7.2 and 1.8.0 with records
> containing laps.
>
> There's a couple of significant changes I have just committed related
> to the data upgrade functionality:
Thanks guys for the sample data files. I have now verified the upgrade
to version 1.9.0 works from 1.7.1, 1.7.2 and 1.8.0 with records
containing laps.
There's a couple of significant changes I have just committed related
to the data upgrade functionality:
1. I have deleted the "check" start up o
Hello Nathan,
Am Samstag, den 22.10.2011, 20:51 +1300 schrieb Nathan Jones:
> There is still a few migrations which I need to fix - basically
> anything in the "checkDBIntegrity" function should be moved into the
> migrate scripts. In order to test this though I need to have some GPX
> files whic
Nathan Jones schrieb am 22.10.2011 09:51:
> I don't have a GPS device so
> could someone please send me some sample GPX files with lap
> information?
sent via PM
cu
Arnd
--
The demand for IT networking professionals con
> Somehow I missed the schema change in revision 662 when rebuilding the
> upgrade scripts so upgrading from 1.7.2 to 1.9.0 fails.
The issue was that I neglected to move the "check db" code for record
duration from ddbb.py into the add record duration upgrade script. I
have fixed this in revision
I've just found another issue which needs to be fixed before release.
Somehow I missed the schema change in revision 662 when rebuilding the
upgrade scripts so upgrading from 1.7.2 to 1.9.0 fails. I'll fix this
ASAP.
- Nathan
--
File "/usr/lib/python2.7/site-packages/pytrainer/stats.py", line 55,
in get_stats
sport = self._sport_service.get_sport(r['sport'])
File "/usr/lib/python2.7/site-packages/pytrainer/sport.py", line
148, in get_sport
raise ValueError("Sport id cannot be None")
>>
>>> File "/usr/lib/python2.7/site-packages/pytrainer/stats.py", line 55,
>>> in get_stats
>>> sport = self._sport_service.get_sport(r['sport'])
>>> File "/usr/lib/python2.7/site-packages/pytrainer/sport.py", line
>>> 148, in get_sport
>>> raise ValueError("Sport id cannot be None")
>>> Valu
Hi,
>> Actually yes. I follow a simpler approach so no changes in database
>> are needed: standard duration is active one and difference with total
>> one is shown (and on-the-fly calculated) just in main subtab under
>> register one. Still need to do some tests, migration script (for
>> database
On 28 August 2011 02:13, David García Granda wrote:
>
> Actually yes. I follow a simpler approach so no changes in database
> are needed: standard duration is active one and difference with total
> one is shown (and on-the-fly calculated) just in main subtab under
> register one. Still need to do
Hi,
2011/8/27 Nathan Jones :
>> >From my side just two issues I would like to fix before releasing 1.9.0:
>>
>> - Using "active" activity duration instead total one for calculations
>> (ticket https://sourceforge.net/apps/trac/pytrainer/ticket/103)
>> - Problems with resizing (ticket
>> https://so
> >From my side just two issues I would like to fix before releasing 1.9.0:
>
> - Using "active" activity duration instead total one for calculations
> (ticket https://sourceforge.net/apps/trac/pytrainer/ticket/103)
> - Problems with resizing (ticket
> https://sourceforge.net/apps/trac/pytrainer/ti
Hi Noël,
> I don't want to pester but since 1.8.0 (Okt 2010) the svn has alot of
> fixes and features which don't reach the user.
Absolutely true.
> The version number doesn't matter so much IMHO (thread "Updating version
> number") but releasing the fine new features.:)
Don't tell Nathan ;-)
This is doable and is probably a good idea. We will need to do some
thorough testing, especially around the new automatic data upgrade
framework - https://sourceforge.net/apps/trac/pytrainer/ticket/132
I was hoping to finish the service layer refactoring -
https://sourceforge.net/apps/trac/pytrain
Hello,
I don't want to pester but since 1.8.0 (Okt 2010) the svn has alot of
fixes and features which don't reach the user.
The version number doesn't matter so much IMHO (thread "Updating version
number") but releasing the fine new features.:)
We (the pytrainer Debian packager and Ubuntu uses the
17 matches
Mail list logo
