sqlobject-discuss — All things SQLObject-related

[SQLObject] Development news

[Oleg B. <ph...@ph...>]

Hello! With the recent activity in master I'm going to release version
3.1. I declare older branches unsupported.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3 and FormEncode

[Oleg B. <ph...@ph...>]

On Mon, Jul 25, 2016 at 07:55:48AM -0500, Ian Cordasco <gra...@gm...> wrote:
> On Mon, Jul 25, 2016 at 7:51 AM, Christoph Zwerschke <ci...@on...> wrote:
> > Am 25.07.2016 um 13:18 schrieb Oleg Broytman:
> >  >   File "<stdin>", line 1, in <module>
> >  > NameError: name 'unicode' is not defined
> >
> > Hi Oleg,
> >
> > FormEncode 1.3 should run with Python 3, it uses 2to3. This error
> > indicates that during installation the 2to3 tool did not run properly.
> > Some have reported that this problem can be caused by cached wheels.
> >
> > In FormEncode 2, 2to3 is not used any more because of such issues, but I
> > think there is no official release of FormEncode 2 yet.
> >
> > Anyway, if FormEncode 1.3 is installed properly, it should work.
> 
> So this is because FormEncode 1.3 claims it can provide a universal
> wheel (https://github.com/formencode/formencode/blob/1.3.0/setup.cfg#L29)
> but it cannot. A 1.3.1 release should be provided with universal = 0.
> This way when pip caches the wheel it produces, it tags it with py2 or
> py3 as appropriate.

   I see you reported the problem at
https://github.com/formencode/formencode/issues/117
   Thanks!

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3 and FormEncode

[Ian C. <gra...@gm...>]

On Mon, Jul 25, 2016 at 7:55 AM, Ian Cordasco
<gra...@gm...> wrote:
> On Mon, Jul 25, 2016 at 7:51 AM, Christoph Zwerschke <ci...@on...> wrote:
>> Am 25.07.2016 um 13:18 schrieb Oleg Broytman:
>>  >   File "<stdin>", line 1, in <module>
>>  > NameError: name 'unicode' is not defined
>>
>> Hi Oleg,
>>
>> FormEncode 1.3 should run with Python 3, it uses 2to3. This error
>> indicates that during installation the 2to3 tool did not run properly.
>> Some have reported that this problem can be caused by cached wheels.
>>
>> In FormEncode 2, 2to3 is not used any more because of such issues, but I
>> think there is no official release of FormEncode 2 yet.
>>
>> Anyway, if FormEncode 1.3 is installed properly, it should work.
>
> So this is because FormEncode 1.3 claims it can provide a universal
> wheel (https://github.com/formencode/formencode/blob/1.3.0/setup.cfg#L29)
> but it cannot. A 1.3.1 release should be provided with universal = 0.
> This way when pip caches the wheel it produces, it tags it with py2 or
> py3 as appropriate.

I submitted https://github.com/formencode/formencode/issues/117 to see
if we can alleviate this.

Re: [SQLObject] Python 3 and FormEncode

[Oleg B. <ph...@ph...>]

On Mon, Jul 25, 2016 at 02:51:03PM +0200, Christoph Zwerschke <ci...@on...> wrote:
> Am 25.07.2016 um 13:18 schrieb Oleg Broytman:
>  >   File "<stdin>", line 1, in <module>
>  > NameError: name 'unicode' is not defined
> 
> Hi Oleg,
> 
> FormEncode 1.3 should run with Python 3, it uses 2to3. This error 
> indicates that during installation the 2to3 tool did not run properly. 
> Some have reported that this problem can be caused by cached wheels.
> 
> In FormEncode 2, 2to3 is not used any more because of such issues, but I 
> think there is no official release of FormEncode 2 yet.
> 
> Anyway, if FormEncode 1.3 is installed properly, it should work.
> 
> -- Christoph

   Thank you very much! That increases assurance in our tests.

   I've used star-destroyer to fix `import *`, fixed some tests manually
and need to be sure I didn't break anything, so I ran tests with Python
2.7 and 3.4 -- and oops, got these problems with FormEncode.
   Now with FormEncode from git repo I can run tests -- and already
caught a minor bug.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3 and FormEncode

[Ian C. <gra...@gm...>]

On Mon, Jul 25, 2016 at 7:51 AM, Christoph Zwerschke <ci...@on...> wrote:
> Am 25.07.2016 um 13:18 schrieb Oleg Broytman:
>  >   File "<stdin>", line 1, in <module>
>  > NameError: name 'unicode' is not defined
>
> Hi Oleg,
>
> FormEncode 1.3 should run with Python 3, it uses 2to3. This error
> indicates that during installation the 2to3 tool did not run properly.
> Some have reported that this problem can be caused by cached wheels.
>
> In FormEncode 2, 2to3 is not used any more because of such issues, but I
> think there is no official release of FormEncode 2 yet.
>
> Anyway, if FormEncode 1.3 is installed properly, it should work.

So this is because FormEncode 1.3 claims it can provide a universal
wheel (https://github.com/formencode/formencode/blob/1.3.0/setup.cfg#L29)
but it cannot. A 1.3.1 release should be provided with universal = 0.
This way when pip caches the wheel it produces, it tags it with py2 or
py3 as appropriate.

Re: [SQLObject] Python 3 and FormEncode

[Christoph Z. <ci...@on...>]

Am 25.07.2016 um 13:18 schrieb Oleg Broytman:
 >   File "<stdin>", line 1, in <module>
 > NameError: name 'unicode' is not defined

Hi Oleg,

FormEncode 1.3 should run with Python 3, it uses 2to3. This error 
indicates that during installation the 2to3 tool did not run properly. 
Some have reported that this problem can be caused by cached wheels.

In FormEncode 2, 2to3 is not used any more because of such issues, but I 
think there is no official release of FormEncode 2 yet.

Anyway, if FormEncode 1.3 is installed properly, it should work.

-- Christoph

Re: [SQLObject] Python 3 and FormEncode

[Neil M. <drn...@gm...>]

On 25 July 2016 at 13:18, Oleg Broytman <ph...@ph...> wrote:
>
> Hi!
>
> On Mon, Jul 25, 2016 at 01:03:33PM +0200, Neil Muller <drn...@gm...> wrote:
> > On 25 July 2016 at 12:40, Oleg Broytman <ph...@ph...> wrote:
> > > Does anybody here use SQLObject with Python 3? I started to believe it's
> > > still impossible due to FormEncode not being ready for Python 3.4. But
> > > our tests at Travis are passing. So I thing there is something wrong
> > > significantly with the tests. Either Travis or Tox are betraying us.
> >
> > As far as I'm aware, no-one has reported significant issues with formencode
> > 1.3.0 and python 3.4 .
> > Formencode passes it's own test suite on python 3.4, and has for quite some
> > time.
> > https://travis-ci.org/formencode/formencode
> >
> > For the record, I am succesfully running a couple of programs using
> > SQLObject 3 and python 3.4.
> >
> > The python3 Debian package build for sqlobject also runs the test suite, so
> > it's not just passing the tests in the travis environment
> > https://buildd.debian.org/status/fetch.php?pkg=sqlobject&arch=all&ver=3.0.0%2Bdfsg-2&stamp=1469130355
> > (although
> > that's only with python 3.5)
>
>    Thank you! Than there is something wrong with me:
>
> $ mkvirtualenv -p python3.4 SQLObject-py3
> Running virtualenv with interpreter /usr/bin/python3.4
>
> $ pip3 install SQLObject
> Collecting SQLObject
>   Using cached SQLObject-3.0.0-py2.py3-none-any.whl
> Collecting PyDispatcher>=2.0.4 (from SQLObject)
> Collecting FormEncode>=1.1.1 (from SQLObject)
> Installing collected packages: PyDispatcher, FormEncode, SQLObject
> Successfully installed FormEncode-1.3.0 PyDispatcher-2.0.5 SQLObject-3.0.0
>
> $ python3.4 -c "from sqlobject import col"
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/__init__.py", line 8, in <module>
>     from .col import *  # noqa
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/col.py", line 31, in <module>
>     from formencode import compound, validators
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/__init__.py", line 3, in <module>
>     from formencode.api import (
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", line 109, in <module>
>     class Invalid(Exception):
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", line 153, in Invalid
>     if unicode is not str:  # Python 2
> NameError: name 'unicode' is not defined

Formencode 1.3.0 builds with 2to3, and that should replace all the
references to unicode (and it does for me locally - the corresponding
line in my installed package is

"if str is not str:  # Python 2"

Somehow, 2to3 isn't being run correctly in your case, which is puzzling

-- 
Neil Muller
drn...@gm...

I've got a gmail account. Why haven't I become cool?

Re: [SQLObject] Python 3 and FormEncode

[Oleg B. <ph...@ph...>]

On Mon, Jul 25, 2016 at 06:25:08AM -0500, Ian Cordasco <gra...@gm...> wrote:
> So current master (I think) probably has this fixed:
> https://github.com/formencode/formencode/blob/203bb759cd21ca54dddae9772157342d477b45cd/formencode/api.py#L155

   That works:

$ pip3 install git+https://github.com/formencode/formencode
Collecting git+https://github.com/formencode/formencode
  Cloning https://github.com/formencode/formencode to /tmp/pip-tr0kff4o-build
Collecting six (from FormEncode==2.0.0a1)
  Downloading six-1.10.0-py2.py3-none-any.whl
Installing collected packages: six, FormEncode
  Found existing installation: FormEncode 1.3.0
    Uninstalling FormEncode-1.3.0:
      Successfully uninstalled FormEncode-1.3.0
  Running setup.py install for FormEncode ... done
Successfully installed FormEncode-2.0.0a1 six-1.10.0

$ python3.4 -c "from sqlobject import col"

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Python 3, FormEncode, Travis, Tox

[Oleg B. <ph...@ph...>]

On Mon, Jul 25, 2016 at 06:25:08AM -0500, Ian Cordasco <gra...@gm...> wrote:
> So current master (I think) probably has this fixed:
> https://github.com/formencode/formencode/blob/203bb759cd21ca54dddae9772157342d477b45cd/formencode/api.py#L155
> 
> You can see what it was in 1.3.0:
> https://github.com/formencode/formencode/blob/1.3.0/formencode/api.py#L153

   But how does it work in our tests? We use exactly that, FormEncode
1.3.0 from PyPI, not from their git repo:
https://travis-ci.org/sqlobject/sqlobject/jobs/143714752

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3 and FormEncode

[Ian C. <gra...@gm...>]

On Mon, Jul 25, 2016 at 6:18 AM, Oleg Broytman <ph...@ph...> wrote:
> Hi!
>
> On Mon, Jul 25, 2016 at 01:03:33PM +0200, Neil Muller <drn...@gm...> wrote:
>> On 25 July 2016 at 12:40, Oleg Broytman <ph...@ph...> wrote:
>> > Does anybody here use SQLObject with Python 3? I started to believe it's
>> > still impossible due to FormEncode not being ready for Python 3.4. But
>> > our tests at Travis are passing. So I thing there is something wrong
>> > significantly with the tests. Either Travis or Tox are betraying us.
>>
>> As far as I'm aware, no-one has reported significant issues with formencode
>> 1.3.0 and python 3.4 .
>> Formencode passes it's own test suite on python 3.4, and has for quite some
>> time.
>> https://travis-ci.org/formencode/formencode
>>
>> For the record, I am succesfully running a couple of programs using
>> SQLObject 3 and python 3.4.
>>
>> The python3 Debian package build for sqlobject also runs the test suite, so
>> it's not just passing the tests in the travis environment
>> https://buildd.debian.org/status/fetch.php?pkg=sqlobject&arch=all&ver=3.0.0%2Bdfsg-2&stamp=1469130355
>> (although
>> that's only with python 3.5)
>
>    Thank you! Than there is something wrong with me:
>
> $ mkvirtualenv -p python3.4 SQLObject-py3
> Running virtualenv with interpreter /usr/bin/python3.4
>
> $ pip3 install SQLObject
> Collecting SQLObject
>   Using cached SQLObject-3.0.0-py2.py3-none-any.whl
> Collecting PyDispatcher>=2.0.4 (from SQLObject)
> Collecting FormEncode>=1.1.1 (from SQLObject)
> Installing collected packages: PyDispatcher, FormEncode, SQLObject
> Successfully installed FormEncode-1.3.0 PyDispatcher-2.0.5 SQLObject-3.0.0
>
> $ python3.4 -c "from sqlobject import col"
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/__init__.py", line 8, in <module>
>     from .col import *  # noqa
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/col.py", line 31, in <module>
>     from formencode import compound, validators
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/__init__.py", line 3, in <module>
>     from formencode.api import (
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", line 109, in <module>
>     class Invalid(Exception):
>   File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", line 153, in Invalid
>     if unicode is not str:  # Python 2
> NameError: name 'unicode' is not defined

So current master (I think) probably has this fixed:
https://github.com/formencode/formencode/blob/203bb759cd21ca54dddae9772157342d477b45cd/formencode/api.py#L155

You can see what it was in 1.3.0:
https://github.com/formencode/formencode/blob/1.3.0/formencode/api.py#L153

That team is likely struggling with Python 3 compatibility, but I
think they probably just need to release a bug fix for 1.3.0 for
people using Python 3.

I asked the FormEncode team for a new release:
https://github.com/formencode/formencode/issues/104#issuecomment-234927875

Re: [SQLObject] Python 3 and FormEncode

[Oleg B. <ph...@ph...>]

Hi!

On Mon, Jul 25, 2016 at 01:03:33PM +0200, Neil Muller <drn...@gm...> wrote:
> On 25 July 2016 at 12:40, Oleg Broytman <ph...@ph...> wrote:
> > Does anybody here use SQLObject with Python 3? I started to believe it's
> > still impossible due to FormEncode not being ready for Python 3.4. But
> > our tests at Travis are passing. So I thing there is something wrong
> > significantly with the tests. Either Travis or Tox are betraying us.
> 
> As far as I'm aware, no-one has reported significant issues with formencode
> 1.3.0 and python 3.4 .
> Formencode passes it's own test suite on python 3.4, and has for quite some
> time.
> https://travis-ci.org/formencode/formencode
> 
> For the record, I am succesfully running a couple of programs using
> SQLObject 3 and python 3.4.
> 
> The python3 Debian package build for sqlobject also runs the test suite, so
> it's not just passing the tests in the travis environment
> https://buildd.debian.org/status/fetch.php?pkg=sqlobject&arch=all&ver=3.0.0%2Bdfsg-2&stamp=1469130355
> (although
> that's only with python 3.5)

   Thank you! Than there is something wrong with me:

$ mkvirtualenv -p python3.4 SQLObject-py3
Running virtualenv with interpreter /usr/bin/python3.4

$ pip3 install SQLObject
Collecting SQLObject
  Using cached SQLObject-3.0.0-py2.py3-none-any.whl
Collecting PyDispatcher>=2.0.4 (from SQLObject)
Collecting FormEncode>=1.1.1 (from SQLObject)
Installing collected packages: PyDispatcher, FormEncode, SQLObject
Successfully installed FormEncode-1.3.0 PyDispatcher-2.0.5 SQLObject-3.0.0

$ python3.4 -c "from sqlobject import col"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/__init__.py", line 8, in <module>
    from .col import *  # noqa
  File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/sqlobject/col.py", line 31, in <module>
    from formencode import compound, validators
  File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/__init__.py", line 3, in <module>
    from formencode.api import (
  File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", line 109, in <module>
    class Invalid(Exception):
  File "/home/phd/.virtualenvs/SQLObject-py3/lib/python3.4/site-packages/formencode/api.py", line 153, in Invalid
    if unicode is not str:  # Python 2
NameError: name 'unicode' is not defined

$ python3.4 
Python 3.4.2 (default, Oct  8 2014, 13:14:40) 
[GCC 4.9.1] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> unicode
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'unicode' is not defined

> -- 
> Neil Muller
> drn...@gm...
> 
> I've got a gmail account. Why haven't I become cool?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3, FormEncode, Travis, Tox

[Neil M. <drn...@gm...>]

On 25 July 2016 at 12:40, Oleg Broytman <ph...@ph...> wrote:
> Does anybody here use SQLObject with Python 3? I started to believe it's
> still impossible due to FormEncode not being ready for Python 3.4. But
> our tests at Travis are passing. So I thing there is something wrong
> significantly with the tests. Either Travis or Tox are betraying us.

As far as I'm aware, no-one has reported significant issues with formencode
1.3.0 and python 3.4 .
Formencode passes it's own test suite on python 3.4, and has for quite some
time.
https://travis-ci.org/formencode/formencode

For the record, I am succesfully running a couple of programs using
SQLObject 3 and python 3.4.

The python3 Debian package build for sqlobject also runs the test suite, so
it's not just passing the tests in the travis environment
https://buildd.debian.org/status/fetch.php?pkg=sqlobject&arch=all&ver=3.0.0%2Bdfsg-2&stamp=1469130355
(although
that's only with python 3.5)


-- 
Neil Muller
drn...@gm...

I've got a gmail account. Why haven't I become cool?

[SQLObject] Python 3, FormEncode, Travis, Tox

[Oleg B. <ph...@ph...>]

Does anybody here use SQLObject with Python 3? I started to believe it's
still impossible due to FormEncode not being ready for Python 3.4. But
our tests at Travis are passing. So I thing there is something wrong
significantly with the tests. Either Travis or Tox are betraying us.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] postgresql json/jsonb

[Oleg B. <ph...@ph...>]

On Tue, Jun 28, 2016 at 04:31:50PM +0200, Lutz Steinborn <l.s...@4c...> wrote:
> Hello,

Hi!

> is where a way to use sqlobject with json/jsonb data type from
> postgresql? I didn't find anything in the docs about this.
> 
> Creating tables isn't the issue (hello psql) but how to
> select/insert/update?

   SQLObject doesn't currently support JSON. Do you want to work on
adding such support?

> Kindly regards and thank you for all the work.
> 
> Lutz Steinborn

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] postgresql json/jsonb

[Lutz S. <l.s...@4c...>]

Hello,

is where a way to use sqlobject with json/jsonb data type from
postgresql? I didn't find anything in the docs about this.

Creating tables isn't the issue (hello psql) but how to
select/insert/update?

Kindly regards and thank you for all the work.

Lutz Steinborn

Re: [SQLObject] SQLObject 3.0.0

[Oleg B. <ph...@ph...>]

The development was never stopped, just slowed. And I'm always longing
for your pull requests, people!

On Thu, Jun 02, 2016 at 09:37:34PM +0200, Jerome Kerdreux <jk...@la...> wrote:
> 
> 
> Yes ! .. SQLObject is back to business ;)
> 
> 
> Bye
> 
> On 06/02/2016 07:18 PM, Gustavo A. D?az wrote:
> >Great work!!
> >
> >Thanks.
> >
> >-- 
> >Gustavo A. D?az
> >GDNet - www.gdnet.com.ar <http://www.gdnet.com.ar>
> >"Servicios TI para tus necesidades"
> >
> >2016-06-01 13:00 GMT-03:00 Oleg Broytman <ph...@ph...
> ><mailto:ph...@ph...>>:
> >
> >    Hello!
> >
> >    I'm pleased to announce version 3.0.0, the first stable release of
> >    branch
> >    3.0 of SQLObject.
> >
> >
> >    What's new in SQLObject
> >    =======================
> >
> >    Features
> >    --------
> >
> >    * Support for Python 2 and Python 3 with one codebase!
> >      (Python version >= 3.4 currently required.)
> >
> >    Minor features
> >    --------------
> >
> >    * PyDispatcher (>=2.0.4) was made an external dependency.
> >
> >    Development
> >    -----------
> >
> >    * Source code was made flake8-clean.
> >
> >    Documentation
> >    -------------
> >
> >    * Documentation is published at http://sqlobject.readthedocs.org/ in
> >      Sphinx format.
> >
> >    Contributors for this release are Ian Cordasco, Neil Muller,
> >    Lukasz Dobrzanski, Gregor Horvath, Nathan Edwards.
> >
> >    For a more complete list, please see the news:
> >    http://sqlobject.org/News.html
> >
> >
> >    What is SQLObject
> >    =================
> >
> >    SQLObject is an object-relational mapper.  Your database tables
> >    are described
> >    as classes, and rows are instances of those classes. SQLObject is
> >    meant to be
> >    easy to use and quick to get started with.
> >
> >    SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
> >    Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
> >
> >    Python 2.6, 2.7 or 3.4+ is required.
> >
> >
> >    Where is SQLObject
> >    ==================
> >
> >    Site:
> >    http://sqlobject.org
> >
> >    Development:
> >    http://sqlobject.org/devel/
> >
> >    Mailing list:
> >    https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
> >
> >    Archives:
> >    http://news.gmane.org/gmane.comp.python.sqlobject
> >
> >    Download:
> >    https://pypi.python.org/pypi/SQLObject/3.0.0
> >
> >    News and changes:
> >    http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] SQLObject 3.0.0

[Jerome K. <jk...@la...>]

Yes ! .. SQLObject is back to business ;)


Bye

On 06/02/2016 07:18 PM, Gustavo A. Díaz wrote:
> Great work!!
>
> Thanks.
>
> -- 
> Gustavo A. Díaz
> GDNet - www.gdnet.com.ar <http://www.gdnet.com.ar>
> "Servicios TI para tus necesidades"
>
> 2016-06-01 13:00 GMT-03:00 Oleg Broytman <ph...@ph... 
> <mailto:ph...@ph...>>:
>
>     Hello!
>
>     I'm pleased to announce version 3.0.0, the first stable release of
>     branch
>     3.0 of SQLObject.
>
>
>     What's new in SQLObject
>     =======================
>
>     Features
>     --------
>
>     * Support for Python 2 and Python 3 with one codebase!
>       (Python version >= 3.4 currently required.)
>
>     Minor features
>     --------------
>
>     * PyDispatcher (>=2.0.4) was made an external dependency.
>
>     Development
>     -----------
>
>     * Source code was made flake8-clean.
>
>     Documentation
>     -------------
>
>     * Documentation is published at http://sqlobject.readthedocs.org/ in
>       Sphinx format.
>
>     Contributors for this release are Ian Cordasco, Neil Muller,
>     Lukasz Dobrzanski, Gregor Horvath, Nathan Edwards.
>
>     For a more complete list, please see the news:
>     http://sqlobject.org/News.html
>
>
>     What is SQLObject
>     =================
>
>     SQLObject is an object-relational mapper.  Your database tables
>     are described
>     as classes, and rows are instances of those classes. SQLObject is
>     meant to be
>     easy to use and quick to get started with.
>
>     SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
>     Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
>
>     Python 2.6, 2.7 or 3.4+ is required.
>
>
>     Where is SQLObject
>     ==================
>
>     Site:
>     http://sqlobject.org
>
>     Development:
>     http://sqlobject.org/devel/
>
>     Mailing list:
>     https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
>
>     Archives:
>     http://news.gmane.org/gmane.comp.python.sqlobject
>
>     Download:
>     https://pypi.python.org/pypi/SQLObject/3.0.0
>
>     News and changes:
>     http://sqlobject.org/News.html
>
>     Oleg.
>     --
>          Oleg Broytman http://phdru.name/ ph...@ph...
>     <mailto:ph...@ph...>
>                Programmers don't die, they just GOSUB without RETURN.
>
>     ------------------------------------------------------------------------------
>     What NetFlow Analyzer can do for you? Monitors network bandwidth
>     and traffic
>     patterns at an interface-level. Reveals which users, apps, and
>     protocols are
>     consuming the most bandwidth. Provides multi-vendor support for
>     NetFlow,
>     J-Flow, sFlow and other flows. Make informed decisions using capacity
>     planning reports.
>     https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>     _______________________________________________
>     sqlobject-discuss mailing list
>     sql...@li...
>     <mailto:sql...@li...>
>     https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>
>
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss

Re: [SQLObject] SQLObject 3.0.0

[Oleg B. <ph...@ph...>]

Hi! Thank you! And many thanks to all who made this happen!

On Thu, Jun 02, 2016 at 02:18:40PM -0300, "Gustavo A. D??az" <gus...@gm...> wrote:
> Great work!!
> 
> Thanks.
> 
> -- 
> Gustavo A. D??az
> GDNet - www.gdnet.com.ar
> "Servicios TI para tus necesidades"
> 
> 2016-06-01 13:00 GMT-03:00 Oleg Broytman <ph...@ph...>:
> 
> > Hello!
> >
> > I'm pleased to announce version 3.0.0, the first stable release of branch
> > 3.0 of SQLObject.
> >
> >
> > What's new in SQLObject
> > =======================
> >
> > Features
> > --------
> >
> > * Support for Python 2 and Python 3 with one codebase!
> >   (Python version >= 3.4 currently required.)
> >
> > Minor features
> > --------------
> >
> > * PyDispatcher (>=2.0.4) was made an external dependency.
> >
> > Development
> > -----------
> >
> > * Source code was made flake8-clean.
> >
> > Documentation
> > -------------
> >
> > * Documentation is published at http://sqlobject.readthedocs.org/ in
> >   Sphinx format.
> >
> > Contributors for this release are Ian Cordasco, Neil Muller,
> > Lukasz Dobrzanski, Gregor Horvath, Nathan Edwards.
> >
> > For a more complete list, please see the news:
> > http://sqlobject.org/News.html
> >
> >
> > What is SQLObject
> > =================
> >
> > SQLObject is an object-relational mapper.  Your database tables are
> > described
> > as classes, and rows are instances of those classes.  SQLObject is meant
> > to be
> > easy to use and quick to get started with.
> >
> > SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
> > Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
> >
> > Python 2.6, 2.7 or 3.4+ is required.
> >
> >
> > Where is SQLObject
> > ==================
> >
> > Site:
> > http://sqlobject.org
> >
> > Development:
> > http://sqlobject.org/devel/
> >
> > Mailing list:
> > https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
> >
> > Archives:
> > http://news.gmane.org/gmane.comp.python.sqlobject
> >
> > Download:
> > https://pypi.python.org/pypi/SQLObject/3.0.0
> >
> > News and changes:
> > http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] SQLObject 3.0.0

[Gustavo A. D. <gus...@gm...>]

Great work!!

Thanks.

-- 
Gustavo A. Díaz
GDNet - www.gdnet.com.ar
"Servicios TI para tus necesidades"

2016-06-01 13:00 GMT-03:00 Oleg Broytman <ph...@ph...>:

> Hello!
>
> I'm pleased to announce version 3.0.0, the first stable release of branch
> 3.0 of SQLObject.
>
>
> What's new in SQLObject
> =======================
>
> Features
> --------
>
> * Support for Python 2 and Python 3 with one codebase!
>   (Python version >= 3.4 currently required.)
>
> Minor features
> --------------
>
> * PyDispatcher (>=2.0.4) was made an external dependency.
>
> Development
> -----------
>
> * Source code was made flake8-clean.
>
> Documentation
> -------------
>
> * Documentation is published at http://sqlobject.readthedocs.org/ in
>   Sphinx format.
>
> Contributors for this release are Ian Cordasco, Neil Muller,
> Lukasz Dobrzanski, Gregor Horvath, Nathan Edwards.
>
> For a more complete list, please see the news:
> http://sqlobject.org/News.html
>
>
> What is SQLObject
> =================
>
> SQLObject is an object-relational mapper.  Your database tables are
> described
> as classes, and rows are instances of those classes.  SQLObject is meant
> to be
> easy to use and quick to get started with.
>
> SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
> Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
>
> Python 2.6, 2.7 or 3.4+ is required.
>
>
> Where is SQLObject
> ==================
>
> Site:
> http://sqlobject.org
>
> Development:
> http://sqlobject.org/devel/
>
> Mailing list:
> https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
>
> Archives:
> http://news.gmane.org/gmane.comp.python.sqlobject
>
> Download:
> https://pypi.python.org/pypi/SQLObject/3.0.0
>
> News and changes:
> http://sqlobject.org/News.html
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

[SQLObject] SQLObject 3.0.0

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 3.0.0, the first stable release of branch
3.0 of SQLObject.


What's new in SQLObject
=======================

Features
--------

* Support for Python 2 and Python 3 with one codebase!
  (Python version >= 3.4 currently required.)

Minor features
--------------

* PyDispatcher (>=2.0.4) was made an external dependency.

Development
-----------

* Source code was made flake8-clean.

Documentation
-------------

* Documentation is published at http://sqlobject.readthedocs.org/ in
  Sphinx format.

Contributors for this release are Ian Cordasco, Neil Muller,
Lukasz Dobrzanski, Gregor Horvath, Nathan Edwards.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6, 2.7 or 3.4+ is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/3.0.0

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 3.0.0b1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 3.0.0b1, the first beta of the upcoming
release of branch 3.0 of SQLObject.


What's new in SQLObject
=======================

Features
--------

* Support for Python 2 and Python 3 with one codebase!
  (Python version >= 3.4 currently required.)

Minor features
--------------

* PyDispatcher (>=2.0.4) was made an external dependency.

Development
-----------

* Source code was made flake8-clean.

Documentation
-------------

* Documentation is published at http://sqlobject.readthedocs.org/ in
  Sphinx format.

Contributors for this release are Ian Cordasco, Neil Muller,
Lukasz Dobrzanski, Gregor Horvath, Nathan Edwards.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6, 2.7 or 3.4+ is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/3.0.0b1

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 2.2.1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 2.2.1, the first bugfix release of branch
2.2 of SQLObject.


What's new in SQLObject
=======================

* Fix a bug in sqlbuilder.CONCAT (inherit from SQLExpression).

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6 or 2.7 is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.2.1

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 2.2

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 2.2.0, the first stable release of branch
2.2 of SQLObject.


What's new in SQLObject
=======================

Features & Interface
--------------------

* Add function col.use_microseconds(True/False). Default is to use
  microseconds (True).

* For MSSQL use datetime2(6) and time(6) columns.

* Columns for ForeignKey are created using idType of the referenced
  table.

Minor features
--------------

* Add sqlbuilder.CONCAT to generate concatenation command (either using
  function CONCAT() or '||' operator).

* Minor refactoring to pave the way to Python 3.

* Document MSSQL server versions.

Bugfixes
--------

* Fix a bug: mxDateTime doesn't support microseconds; %s in mxDateTime
  format means ticks.

Tests
-----

* Speedup SQLite connections in tests.

* Added new test help setupCyclicClasses to setup classes with mutual
  references.

Contributors for this release are Andrew Ziem and Nathan Edwards.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).

Python 2.6 or 2.7 is required.


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.2.0

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Oleg B. <ph...@ph...>]

Hello!

On Fri, Apr 22, 2016 at 05:18:32PM +0200, Neil Muller <drn...@gm...> wrote:
> On 26 March 2015 at 21:47, Neil Muller <drn...@gm...> wrote:
> > On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
> >> Hi! All tests are green. What's next?
> >>
> >
> > I'm currently working on converting a few small'ish programs I have to
> > use python 3 and sqlobject trunk, to see if that shows any lingering
> > issues. Unfortunately, I haven't been able to find a lot of time to
> > work on sqlobject over the last few weeks, so this hasn't been
> > proceeding as quickly as I'd hoped.
> >
> 
> I realise that I never reported back on this. I've now converted
> several programs (of varying levels of complexity) to python 3 and the
> sqlobject 3 alpha release, and other than the unhashable column issue
> that was fixed in January, I haven't encountered any problems due to
> sqlobject.

   Thank you for reporting!

> I would say sqlobject 3 is ready for a full release.

   I am on vacation. Will do a release when I return -- after May 1st.

> -- 
> Neil Muller
> drn...@gm...
> 
> I've got a gmail account. Why haven't I become cool?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Python 3

[Neil M. <drn...@gm...>]

On 26 March 2015 at 21:47, Neil Muller <drn...@gm...> wrote:
> On 26 March 2015 at 21:33, Oleg Broytman <ph...@ph...> wrote:
>> Hi! All tests are green. What's next?
>>
>
> I'm currently working on converting a few small'ish programs I have to
> use python 3 and sqlobject trunk, to see if that shows any lingering
> issues. Unfortunately, I haven't been able to find a lot of time to
> work on sqlobject over the last few weeks, so this hasn't been
> proceeding as quickly as I'd hoped.
>

I realise that I never reported back on this. I've now converted
several programs (of varying levels of complexity) to python 3 and the
sqlobject 3 alpha release, and other than the unhashable column issue
that was fixed in January, I haven't encountered any problems due to
sqlobject.

I would say sqlobject 3 is ready for a full release.

-- 
Neil Muller
drn...@gm...

I've got a gmail account. Why haven't I become cool?