Please correct me if I'm wrong. I thought Web Update would update dabo based on revision number. When I click on the Web Update "Check Now" button to see if there are any updates, it tells me there are no updates available, yet the latest commit (based on dabo-dev) is ~3720.
Is there a problem with Web Update, or do I need to get the latest updates via subversion? A single button click sure seems a lot easier.
Kind regards.
Ruben Baumann
Platform: Win
Python Version: 2.5.1 on win32
Dabo Version: Version 0.8.2; Revision ~3695
UI Version: 2.8.4.0 on wxMSW
---------------------------------
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
On Nov 20, 2007, at 9:08 AM, Ruben and Yvonne Baumann wrote:
> Please correct me if I'm wrong. I thought Web Update would update
> dabo based on revision number. When I click on the Web Update
> "Check Now" button to see if there are any updates, it tells me
> there are no updates available, yet the latest commit (based on
> dabo-dev) is ~3720.
>
> Is there a problem with Web Update, or do I need to get the
> latest updates via subversion? A single button click sure seems a
> lot easier.
You're almost correct. One of the problems with using the latest
Subversion release (besides requiring that Subversion be installed)
is that some changes may be committed that have not been fully tested
yet. If you were to update to those revisions, chances are you could
start getting errors that previously didn't exist in your apps.
So what we do is once a set of changes has been sufficiently tested
so that we feel that the chance of causing problems is fairly small,
that revision is marked as the current Web Update revision. This way,
updating is not only fast and easy, but safe.
-- Ed Leafe
> On Nov 20, 2007, at 9:08 AM, Ruben and Yvonne Baumann wrote:
> Please correct me if I'm wrong. I thought Web Update would update
> dabo based on revision number. When I click on the Web Update
> "Check Now" button to see if there are any updates, it tells me
> there are no updates available, yet the latest commit (based on
> dabo-dev) is ~3720.
>
> Is there a problem with Web Update, or do I need to get the
> latest updates via subversion? A single button click sure seems a
> lot easier.
>> Ed Leafe <ed@leafe.com> wrote:
>> You're almost correct. One of the problems with using the latest
>> Subversion release (besides requiring that Subversion be installed)
>> is that some changes may be committed that have not been fully tested
>> yet. If you were to update to those revisions, chances are you could
>> start getting errors that previously didn't exist in your apps.
>>
>> So what we do is once a set of changes has been sufficiently tested
>> so that we feel that the chance of causing problems is fairly small,
>> that revision is marked as the current Web Update revision. This way,
>> updating is not only fast and easy, but safe.
>> -- Ed Leafe
>> -- http://leafe.com
>> -- http://dabodev.com
OK, thanks, Ed.
Just reviewed an earlier post by Paul that said you guys were going to try and get point releases out every 4-5 weeks. Are you still on schedule for 8.3 in that regard?
Also, I vaguely recall seeing a post that if I _did_ update with subversion, that Web Update would no longer work? or am I confused.
Thanks again.
Kind regards.
Ruben Baumann
---------------------------------
Never miss a thing. Make Yahoo your homepage.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
On Nov 20, 2007 8:43 AM, Ruben and Yvonne Baumann <rynt@yahoo.com> wrote:
>
> > On Nov 20, 2007, at 9:08 AM, Ruben and Yvonne Baumann wrote:
> > Please correct me if I'm wrong. I thought Web Update would update
> > dabo based on revision number. When I click on the Web Update
> > "Check Now" button to see if there are any updates, it tells me
> > there are no updates available, yet the latest commit (based on
> > dabo-dev) is ~3720.
> >
> > Is there a problem with Web Update, or do I need to get the
> > latest updates via subversion? A single button click sure seems a
> > lot easier.
>
> >> Ed Leafe <ed@leafe.com> wrote:
> >> You're almost correct. One of the problems with using the latest
> >> Subversion release (besides requiring that Subversion be installed)
> >> is that some changes may be committed that have not been fully tested
> >> yet. If you were to update to those revisions, chances are you could
> >> start getting errors that previously didn't exist in your apps.
> >>
> >> So what we do is once a set of changes has been sufficiently tested
> >> so that we feel that the chance of causing problems is fairly small,
> >> that revision is marked as the current Web Update revision. This way,
> >> updating is not only fast and easy, but safe.
> >> -- Ed Leafe
> >> -- http://leafe.com
> >> -- http://dabodev.com
>
> OK, thanks, Ed.
>
> Just reviewed an earlier post by Paul that said you guys were going to try and get point releases out every 4-5 weeks. Are you still on schedule for 8.3 in that regard?
>
> Also, I vaguely recall seeing a post that if I _did_ update with subversion, that Web Update would no longer work? or am I confused.
The problem is that you have 2 separate update sources. If you
updated with subversion I am not sure if it would screw up the web
update. However, using subversion and Web Update together will REALLY
mess up subversion. It's either one or the other, not both. For
developer's of apps using dabo, it is better to use web update. For
people that actually contribute code to the framework, it is not only
better but necessary to use subversion.
Hope this clears things up a bit.
Cheers,
Nate L.
On Nov 20, 2007, at 10:43 AM, Ruben and Yvonne Baumann wrote:
> Just reviewed an earlier post by Paul that said you guys were
> going to try and get point releases out every 4-5 weeks. Are you
> still on schedule for 8.3 in that regard?
Paul would be the one to comment on that. He handles all the point
releases.
> Also, I vaguely recall seeing a post that if I _did_ update with
> subversion, that Web Update would no longer work? or am I confused.
It makes no sense to use both, and can cause problems. If you use
both, and then update via Web Update, Subversion doesn't know about
this update and simply sees them as modified files, and may mark them
as conflicted the next time you go to update. Also, it's internal
revision counter will be out of sync with the framework revision file.
The rule of thumb is:
a) If you are developing Dabo itself, you should use Subversion.
b) If you just like having the bleeding edge code, use Subversion.
c) Otherwise, use Web Update.
-- Ed Leafe
>Nate Lowrie <solodex2151@gmail.com> wrote:
>The problem is that you have 2 separate update sources. If you
>updated with subversion I am not sure if it would screw up the web
>update. However, using subversion and Web Update together will REALLY
>mess up subversion. It's either one or the other, not both. For
>developer's of apps using dabo, it is better to use web update. For
>people that actually contribute code to the framework, it is not only
>better but necessary to use subversion.
>Hope this clears things up a bit.
>Cheers,
>Nate L.
Thanks Nate. I appreciate the reply. Guess I'll stick with Web Update.
Kind regards.
Ruben
---------------------------------
Never miss a thing. Make Yahoo your homepage.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
Thanks Ed.
Ruben
Ed Leafe <ed@leafe.com> wrote:
On Nov 20, 2007, at 10:43 AM, Ruben and Yvonne Baumann wrote:
> Just reviewed an earlier post by Paul that said you guys were
> going to try and get point releases out every 4-5 weeks. Are you
> still on schedule for 8.3 in that regard?
Paul would be the one to comment on that. He handles all the point
releases.
> Also, I vaguely recall seeing a post that if I _did_ update with
> subversion, that Web Update would no longer work? or am I confused.
It makes no sense to use both, and can cause problems. If you use
both, and then update via Web Update, Subversion doesn't know about
this update and simply sees them as modified files, and may mark them
as conflicted the next time you go to update. Also, it's internal
revision counter will be out of sync with the framework revision file.
The rule of thumb is:
a) If you are developing Dabo itself, you should use Subversion.
b) If you just like having the bleeding edge code, use Subversion.
c) Otherwise, use Web Update.
-- Ed Leafe
[excessive quoting removed by server]
Ruben and Yvonne Baumann wrote:
> Please correct me if I'm wrong. I thought Web Update would update dabo based on revision number. When I click on the Web Update "Check Now" button to see if there are any updates, it tells me there are no updates available, yet the latest commit (based on dabo-dev) is ~3720.
>
The latest revision for the web update can be found in a FAQ now:
http://dabodev.com/wiki/FAQs#LatestWebUpdateRevisionNumber
HTH,
Uwe
Ed Leafe wrote:
> On Nov 20, 2007, at 10:43 AM, Ruben and Yvonne Baumann wrote:
>
>> Just reviewed an earlier post by Paul that said you guys were
>> going to try and get point releases out every 4-5 weeks. Are you
>> still on schedule for 8.3 in that regard?
>
> Paul would be the one to comment on that. He handles all the point
> releases.
I'd like to do 0.8.3 on 12/1. Unless some new changes seem to be causing
new problems, I'd say we are on schedule. All existing 0.8.3 bugs will
be bumped to 0.8.4, but it would be great if we could focus on clearing
some of those this coming week.
--
pkm ~ http://paulmcnett.com
Author: aklaver@comcast.net (Adrian Klaver)
Posted: 2007-12-03 15:52:38 Link
When I run the update I get:
Traceback (most recent call last):
File
"/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/ui/uiwx/dControlMixi
n.py", line 21, in _onWxHit
self.raiseEvent(dEvents.Hit, evt, *args, **kwargs)
File
"/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/ui/uiwx/dPemMixin.py
", line 843, in raiseEvent
super(dPemMixin, self).raiseEvent(eventClass, nativeEvent, *args, **kwargs)
File
"/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/lib/eventMixin.py",
line 92, in raiseEvent
bindingFunction(event)
File
"/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/ui/dialogs/Preferenc
eDialog.py", line 272, in onCheckNow
ret = self.Application.checkForUpdates()
File "/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/dApp.py",
line 385, in checkForUpdates
return self.uiApp.checkForUpdates(force=True)
File
"/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/ui/uiwx/uiApp.py",
line 187, in checkForUpdates
vers = self.dApp._updateFramework()
File "/usr/lib/python2.5/site-packages/Dabo-0.8.2-py2.5.egg/dabo/dApp.py",
line 455, in _updateFramework
os.mkdirs(localPath)
AttributeError: 'module' object has no attribute 'mkdirs'
I guess os has either mkdir or makedirs. I didn't study the code to see which
one you intend.
--
Adrian Klaver
aklaver@comcast.net