Schevo 2006 June Software Release

[Matthew Scott]

===================================
Schevo 2006 June Software Release
===================================

Orbtech, L.L.C. and the Schevo team are pleased to announce the
availability
of the 2006 June software release of Schevo and related support
packages.

Details and installation information are available at:

http://schevo.org/trac/wiki/SoftwareRelease-2006-06

General information about Schevo is available at:

http://schevo.org/


Upgrades in this release
========================

* Schevo 3.0b2


New packages in this release
============================

* SchevoDot 1.0a1
* SchevoGears 1.0a1
* SchevoGtk 1.0a1
* SchevoSql 1.0a1
* SchevoWeb 1.0a1
* SchevoXml 1.0a1


What is Schevo
==============

Schevo is a next-generation DBMS that focuses on the following:

* **Rapid Development**: Schevo includes features to make it easy and
fun to
create even the most complex of databases. Not only is the schema
syntax
easy to write and understand, you can also quickly place initial
values in
your schema that are required by your database, and use the same
syntax to
create sets of sample data to use during development.

* **User Interface Generation**: Schevo provides user interface
toolkits that
take advantage of the richness of the database schema. You can use
the
full-featured Schevo Navigator to interact with your database without
writing a single line of code outside of your database schema. A
PyQt-based
toolkit is already available, and PyGtk and TurboGears toolkits
are in the
works.

* **Rich Schema Definition**: The schema for a Schevo database is
written in
concise, easy-to-read Python code. Not only does the schema
describe how
information in the database is structured, but also defines all
transactions
and rules that ensure database integrity.

* **Automated Schema Evolution**: Once a Schevo database is deployed
and is
used to store valuable data, you will inevitably make further
changes to the
structure of the database. Schevo assists you in this task and
makes it easy
to restructure a database and facilitate the migration of data
from one
schema version to the next.

* **Transaction Based**: Schevo is designed from the ground up to
protect your
data. All changes to a Schevo database must be done using
transactions, and
Schevo ensures that those transactions always leave the database in a
consistent state.

--
Matthew Scott
***@springfieldtech.com

[Matthew Scott]

Matt-
I'm confused. I know I may be jumping the gun again, but the
annoucement is so official-sounding that it had me hoping for the
best.

Yes, it is official. We tried our best to make sure the code itself
was in a good-enough shape that we could get it out in the wild as
something that can be considered stable and untouched until the next
release. We knew there would be some documentation issues cropping
up and that we would fix them ASAP.

FYI, the current plan is to make a release once a month, and to keep
the API as stable as possible now until the 3.0 final release. Since
we're using branches and tickets now, each monthly release will have
a changelog that lists all of the changes since the last version, and
whether or not the user of Schevo will need to do anything different.

Now that we have made the 3.0b2 release, I'd suggest using the
monthly releases instead of trunk releases from now on, so that it's
easier for you to keep a stable system in place and know details
ahead of time when you decide to upgrade to newer versions.

It took a while to notice that "evo" is now "schevo", but I do see
that in the docs. But then the wiki makes it sound like
"easy_install Schevo" takes care of everything, but since that left
me without a navigator I started easy_install-ing the subpackages,
too. Wanting first to try to get nav, I tried easy_install-ing
SchevoQt, but that doesn't work.

SchevoQt must be licensed under the GNU GPL (because Qt and PyQt
themselves are GPL), instead of the GNU LGPL as with the rest of
Schevo. Also, since new navigator developments are occurring in
SchevoGtk (which is LGPL) and no new developments are occuring in
SchevoQt, we did not make an official announcement of SchevoQt
availability.

That said, it still needed a stable release version in order to
support some Schevo apps that are already deployed and will need
maintenance upgrades. Therefore, you can install version 1.0a1 of
SchevoQt by running this::

easy_install -f http://schevo.org/files/releases SchevoQt

The reason the -f option is needed is because we chose not to
announce SchevoQt on the cheeseshop.

I realize the wiki says it's not under active development, but it's
the only navigator I've used. In search of gnav, I tried
easy_install-ing SchevoGtk, knowing that I was probably in for some
problems, in that the docs have a lot of emphasis on pyQt and
almost nothing on pyGTK. And error I got. First about cairo and
pyGTK, which I then installed manually. But then errors about
FieldLabel and ProxyLabel coming from kiwi.ui.widgets. I now have
kiwi in site-packages from today's install, and a kiwi in share
from about 4 mos. ago. I tried getting rid of share/kiwi in case
of conflict, but that doesn't help.

"schevo nav" should be available once you install SchevoQt as noted
above.

Hopefully by next month's release, we will have worked out the issues
that bar us from gnav being a two-step install. Ideally, those steps
are:

1. Install an official PyGTK distribution for Windows.
2. easy_install SchevoGtk
3. "schevo nav myapp.db" <-- SchevoGtk navigator will
become default "nav"

Stay tuned for that. Sorry about the turmoil; hopefully this
information will help!

--
Matthew Scott
***@springfieldtech.com

[joseph schlesinger]

Post by Matthew Scott

Matt-
I'm confused. I know I may be jumping the gun again, but the
annoucement is so official-sounding that it had me hoping for the best.

Yes, it is official. We tried our best to make sure the code itself
was in a good-enough shape that we could get it out in the wild as
something that can be considered stable and untouched until the next
release. We knew there would be some documentation issues cropping
up and that we would fix them ASAP.
FYI, the current plan is to make a release once a month, and to keep
the API as stable as possible now until the 3.0 final release. Since
we're using branches and tickets now, each monthly release will have
a changelog that lists all of the changes since the last version, and
whether or not the user of Schevo will need to do anything different.
Now that we have made the 3.0b2 release, I'd suggest using the
monthly releases instead of trunk releases from now on, so that it's
easier for you to keep a stable system in place and know details
ahead of time when you decide to upgrade to newer versions.

It took a while to notice that "evo" is now "schevo", but I do see
that in the docs. But then the wiki makes it sound like
"easy_install Schevo" takes care of everything, but since that left
me without a navigator I started easy_install-ing the subpackages,
too. Wanting first to try to get nav, I tried easy_install-ing
SchevoQt, but that doesn't work.

SchevoQt must be licensed under the GNU GPL (because Qt and PyQt
themselves are GPL), instead of the GNU LGPL as with the rest of
Schevo. Also, since new navigator developments are occurring in
SchevoGtk (which is LGPL) and no new developments are occuring in
SchevoQt, we did not make an official announcement of SchevoQt
availability.
That said, it still needed a stable release version in order to
support some Schevo apps that are already deployed and will need
maintenance upgrades. Therefore, you can install version 1.0a1 of
easy_install -f http://schevo.org/files/releases SchevoQt
The reason the -f option is needed is because we chose not to
announce SchevoQt on the cheeseshop.

I realize the wiki says it's not under active development, but it's
the only navigator I've used. In search of gnav, I tried
easy_install-ing SchevoGtk, knowing that I was probably in for some
problems, in that the docs have a lot of emphasis on pyQt and almost
nothing on pyGTK. And error I got. First about cairo and pyGTK,
which I then installed manually. But then errors about FieldLabel
and ProxyLabel coming from kiwi.ui.widgets. I now have kiwi in
site-packages from today's install, and a kiwi in share from about 4
mos. ago. I tried getting rid of share/kiwi in case of conflict,
but that doesn't help.

"schevo nav" should be available once you install SchevoQt as noted
above.
Hopefully by next month's release, we will have worked out the issues
that bar us from gnav being a two-step install. Ideally, those steps
1. Install an official PyGTK distribution for Windows.
2. easy_install SchevoGtk
3. "schevo nav myapp.db" <-- SchevoGtk navigator will become
default "nav"
Stay tuned for that. Sorry about the turmoil; hopefully this
information will help!
--
Matthew Scott

It does help, and as always, thanks for the informative and thoughtful
reply. The new release procedure should go a long way toward helping
me save myself from the constant breakage of my bleeding-edge updates.
But I'm not out of the woods on that yet. After I followed your tip for
installing SchevoQt, I still had the vestiges of my SchevoGtk/unfinished
and/or duplicated kiwi install. I get the traceback reproduced below.
If I'm not wearing out my good will, I'll seek your sagely advice on how
to fix it. :-[


Schevo tracing is ON. See schevo.trace.__doc__ for more information.
Traceback (most recent call last):
File "C:\python24\scripts\schevo-script.py", line 7, in ?
sys.exit(
File
"c:\python24\lib\site-packages\setuptools-0.6b2-py2.4.egg\pkg_resources.p
y", line 236, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File
"c:\python24\lib\site-packages\setuptools-0.6b2-py2.4.egg\pkg_resources.p
y", line 2097, in load_entry_point
return ep.load()
File
"c:\python24\lib\site-packages\setuptools-0.6b2-py2.4.egg\pkg_resources.p
y", line 1830, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File
"c:\python24\lib\site-packages\schevo-3.0b3dev_r2177-py2.4-win32.egg\sche
vo\script\main.py", line 25, in ?
start = Main()
File
"c:\python24\lib\site-packages\schevo-3.0b3dev_r2177-py2.4-win32.egg\sche
vo\script\main.py", line 21, in __init__
command = p.load()
File
"c:\python24\lib\site-packages\setuptools-0.6b2-py2.4.egg\pkg_resources.p
y", line 1830, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File
"c:\python24\lib\site-packages\SchevoGtk-1.0a1-py2.4.egg\schevogtk2\scrip
t.py", line 11, in ?
from schevogtk2.application import Application
File
"c:\python24\lib\site-packages\SchevoGtk-1.0a1-py2.4.egg\schevogtk2\appli
cation.py", line 9, in ?
from schevogtk2 import gazpacholoader
File
"c:\python24\lib\site-packages\SchevoGtk-1.0a1-py2.4.egg\schevogtk2\gazpa
choloader.py", line 4, in ?
from kiwi.environ import environ
File "C:\python24\lib\site-packages\kiwi\__init__.py", line 56, in ?
lib = Library('kiwi')
File "C:\python24\lib\site-packages\kiwi\environ.py", line 211, in
__init__
self.add_global_resources(**module.global_resources)
File "C:\python24\lib\site-packages\kiwi\environ.py", line 235, in
add_global_
resources
self.add_global_resource(resource, path)
File "C:\python24\lib\site-packages\kiwi\environ.py", line 231, in
add_global_
resource
environ.add_resource(resource, os.path.join(self._root, path))
File "C:\python24\lib\site-packages\kiwi\environ.py", line 81, in
add_resource

raise EnvironmentError("path %s must be a directory" % path)
EnvironmentError: path C:\python24\share\kiwi\pixmaps must be a directory

[Patrick K. O'Brien]

Post by joseph schlesinger
It does help, and as always, thanks for the informative and thoughtful
reply. The new release procedure should go a long way toward helping
me save myself from the constant breakage of my bleeding-edge updates.
But I'm not out of the woods on that yet. After I followed your tip for
installing SchevoQt, I still had the vestiges of my SchevoGtk/unfinished
and/or duplicated kiwi install. I get the traceback reproduced below.
If I'm not wearing out my good will, I'll seek your sagely advice on how
to fix it. :-[

The easiest way to resolve this will be on IRC. We have a #schevo
channel on freenode (http://freenode.net/). What I would walk you
through is the following:

1. Delete all evo*.* and schevo*.* files from C:\Python24\Scripts.

2. Delete all schevo*.* files and directories from
C:\Python24\Lib\site-packages.

3. Remove all schevo-related lines from the easy-install.pth file in
C:\Python24\Lib\site-packages.

After all that old stuff is removed, do the following from a command prompt:

4. ez_install Schevo

5. easy_install -f http://schevo.org/files/releases SchevoQt

Then you should be able to do 'schevo qnav'.

[Patrick K. O'Brien]

Post by Patrick K. O'Brien
The easiest way to resolve this will be on IRC. We have a #schevo
channel on freenode (http://freenode.net/). What I would walk you
1. Delete all evo*.* and schevo*.* files from C:\Python24\Scripts.
2. Delete all schevo*.* files and directories from
C:\Python24\Lib\site-packages.
3. Remove all schevo-related lines from the easy-install.pth file in
C:\Python24\Lib\site-packages.
4. ez_install Schevo
5. easy_install -f http://schevo.org/files/releases SchevoQt
Then you should be able to do 'schevo qnav'.

Assuming that you meant "4. easy_install Schevo" (I remember seeing an
"ez_install.py" somewhere but couldn't locate it) following your
instructions solved the problem. Thanks!

Oops. Yes, that is what I meant. I could strangle Philip Eby for using
ez_setup and easy_install in the same toolkit.[1]

[1] But I wouldn't do that... ;-)

[Patrick K. O'Brien]

"schevo nav" should be available once you install SchevoQt as noted above.

Actually, the command for the PyQt navigator is "schevo qnav" and the
PyGTK one is "schevo gnav".