Ian, if you publish here the list of current tasks people could select
some tasks or subtasks to help you.
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@phdru.name
Programmers don't die, they just GOSUB without RETURN.
--
On Thu, Dec 11, 2014 at 8:13 AM, Ian Cordasco
wrote:
> Awesome!
>
> On Dec 11, 2014 8:10 AM, "Oleg Broytman" wrote:
>>
>> On Wed, Dec 10, 2014 at 12:55:36AM +0100, Oleg Broytman
>> wrote:
>> > create a separate branch for 2.0. Then master will be free for working
>> > on Py3 compatibility.
>>
>>
Awesome!
On Dec 11, 2014 8:10 AM, "Oleg Broytman" wrote:
> On Wed, Dec 10, 2014 at 12:55:36AM +0100, Oleg Broytman
> wrote:
> > create a separate branch for 2.0. Then master will be free for working
> > on Py3 compatibility.
>
>Done: I created a new branch 2.0 and edited master to be 3.0
> p
On Wed, Dec 10, 2014 at 12:55:36AM +0100, Oleg Broytman wrote:
> create a separate branch for 2.0. Then master will be free for working
> on Py3 compatibility.
Done: I created a new branch 2.0 and edited master to be 3.0
pre-alpha.
Ian, the master is waiting for you! ;-)
Oleg.
--
Ol
On Wed, Dec 10, 2014 at 12:55:36AM +0100, Oleg Broytman wrote:
>There is one sporadic bug related to round number of microseconds
> like 83500: some parts of code think it's 0.0835 (83500), and some think
> it's 0.835 (835000). See the traceback near the end of
> https://travis-ci.org/sqlobjec
On Wed, Dec 10, 2014 at 12:55:36AM +0100, Oleg Broytman wrote:
> On Sun, Dec 07, 2014 at 08:06:29AM +0100, Oleg Broytman
> wrote:
> >MySQL doesn't support microseconds until 5.6.4, Travis runs
> > 5.5, so the error can be ignored.
> >I will work on skipping the test on backends that don'
On Sun, Dec 07, 2014 at 08:06:29AM +0100, Oleg Broytman wrote:
>MySQL doesn't support microseconds until 5.6.4, Travis runs
> 5.5, so the error can be ignored.
>I will work on skipping the test on backends that don't support
> microseconds and adapt SQLObject to MySQL 5.6.4+ (date/time col
Not sure about completeness but at least there is something to test.
On Mon, Dec 08, 2014 at 02:53:14PM +0100, "Fetchinson ."
wrote:
> On 12/8/14, Oleg Broytman wrote:
> > The new maintainers of FormEncode promised compatibility of version 1.3
> > with Py3: http://www.formencode.org/en/latest/w
On 12/8/14, Oleg Broytman wrote:
> The new maintainers of FormEncode promised compatibility of version 1.3
> with Py3: http://www.formencode.org/en/latest/whatsnew-1.3.html
>They released the first alpha a year ago:
> https://pypi.python.org/pypi/FormEncode and it seems there are commits
> in
The new maintainers of FormEncode promised compatibility of version 1.3
with Py3: http://www.formencode.org/en/latest/whatsnew-1.3.html
They released the first alpha a year ago:
https://pypi.python.org/pypi/FormEncode and it seems there are commits
in the repository since that: https://github.co
Hi all, I've started a python 3 branch of formencde in 2011 but didn't
have time to finish a complete port, you might still find it useful:
https://bitbucket.org/fetchinson/formencode-py3k
To be precise, this is still a python 2 branch, the goal was to have
something which can be fed into 2to3, a
On Mon, Dec 08, 2014 at 02:01:22AM +0100, Oleg Broytman wrote:
> http://docs.travis-ci.com/user/installing-dependencies/
But that doesn't help: Travis runs Ubuntu 12.04 (see
http://docs.travis-ci.com/user/ci-environment/) and it only has MySQL 5.5:
http://packages.ubuntu.com/search?keywords=my
Hi!
On Sun, Dec 07, 2014 at 12:10:16PM -0600, Ian Cordasco
wrote:
> On Sun, Dec 7, 2014 at 1:06 AM, Oleg Broytman wrote:
> > On Fri, Dec 05, 2014 at 08:38:31PM +0100, Oleg Broytman
> > wrote:
> >> datetime test fails with MySQL:
> >
> >Got it: MySQL doesn't support microseconds until 5.6.
On Sun, Dec 7, 2014 at 1:06 AM, Oleg Broytman wrote:
> On Fri, Dec 05, 2014 at 08:38:31PM +0100, Oleg Broytman
> wrote:
>> datetime test fails with MySQL:
>
>Got it: MySQL doesn't support microseconds until 5.6.4, Travis runs
> 5.5, so the error can be ignored.
>I will work on skipping t
On Fri, Dec 05, 2014 at 08:38:31PM +0100, Oleg Broytman wrote:
> datetime test fails with MySQL:
Got it: MySQL doesn't support microseconds until 5.6.4, Travis runs
5.5, so the error can be ignored.
I will work on skipping the test on backends that don't support
microseconds and adapt SQLOb
On Mon, Dec 01, 2014 at 08:53:34AM -0600, Ian Cordasco
wrote:
> First, I've found it far easier to support Python 3 once Python 2.5
> support has been dropped. It is possible to support Python 2.5 (pep8,
> pyflakes, mccabe, and flake8 are all projects which do this) but it is
> tricky. It would b
Woot.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
All tests are passed in branches 1.5, 1.6 and 1.7, and most tests are
passed in master; datetime test fails with MySQL:
https://travis-ci.org/sqlobject/sqlobject/branches
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@phdru.name
Programmers don't die, the
On Thu, Dec 04, 2014 at 08:48:26AM -0600, Ian Cordasco
wrote:
> On Thu, Dec 4, 2014 at 8:39 AM, Oleg Broytman wrote:
> >Later we can change it. BTW, have you tried to run sqlobject's tests
> > with tox? I only run it with py.test.
>
> I haven't tried it yet. Like I said in my first email, m
On Thu, Dec 4, 2014 at 8:39 AM, Oleg Broytman wrote:
> On Thu, Dec 04, 2014 at 08:29:17AM -0600, Ian Cordasco
> wrote:
>> So I tend to have a slightly more complex set-up anyway. (See:
>> https://github.com/sigmavirus24/github3.py/blob/develop/.travis.yml)
>> I've found it easier to do more nuan
On Thu, Dec 04, 2014 at 08:29:17AM -0600, Ian Cordasco
wrote:
> So I tend to have a slightly more complex set-up anyway. (See:
> https://github.com/sigmavirus24/github3.py/blob/develop/.travis.yml)
> I've found it easier to do more nuanced Travis builds with tox and let
> tox handle dependencies
On 4 December 2014 at 16:23, Oleg Broytman wrote:
>> If you make a branch in the repository and (one of us [1]) enables
>> Travis then we can test the config to see how it works :)
>
>Failed with error:
> /home/travis/build.sh: line 41: /usr/bin/py.test: No such file or directory
>See http
On Thu, Dec 4, 2014 at 8:23 AM, Oleg Broytman wrote:
>> If you make a branch in the repository and (one of us [1]) enables
>> Travis then we can test the config to see how it works :)
>
>Failed with error:
> /home/travis/build.sh: line 41: /usr/bin/py.test: No such file or directory
>See h
> If you make a branch in the repository and (one of us [1]) enables
> Travis then we can test the config to see how it works :)
Failed with error:
/home/travis/build.sh: line 41: /usr/bin/py.test: No such file or directory
See https://travis-ci.org/sqlobject/sqlobject/
That's strange, d
On Thu, Dec 4, 2014 at 12:13 AM, Oleg Broytman wrote:
> Hi!
>
> On Mon, Dec 01, 2014 at 08:53:34AM -0600, Ian Cordasco
> wrote:
>> Third, setting up a continuous integration system (like Travis CI) to
>> run the tests after every push and whenever someone submits a pull
>> request. The CI system
On Thu, Dec 04, 2014 at 10:31:48AM +0200, Simon Cross
wrote:
> Travis runs Python builds inside a virtualenv for the selected Python
> version, with a few things pre-installed.
Yes, got it. /usr/bin/python will be either python2.6 of 2.7. Thank
you for spotting!
Oleg.
--
Oleg Broytman
Travis runs Python builds inside a virtualenv for the selected Python
version, with a few things pre-installed.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your
Hi!
On Thu, Dec 04, 2014 at 09:38:04AM +0200, Simon Cross
wrote:
> Looks good?
>
> I was a bit surprised by the "/usr/bin/py.test-$TRAVIS_PYTHON_VERION".
> I would have thought that could just be "py.test"?
But how do you run test with different python versions?
python:
- "2.6"
- "2.7"
Looks good?
I was a bit surprised by the "/usr/bin/py.test-$TRAVIS_PYTHON_VERION".
I would have thought that could just be "py.test"?
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Inst
Hi!
On Mon, Dec 01, 2014 at 08:53:34AM -0600, Ian Cordasco
wrote:
> Third, setting up a continuous integration system (like Travis CI) to
> run the tests after every push and whenever someone submits a pull
> request. The CI system can do the following:
I have always wanted to learn Travis C
On Tue, Dec 02, 2014 at 12:27:29AM +0200, Neil Muller
wrote:
> On 1 December 2014 at 22:49, Oleg Broytman wrote:
> >
> >What's your Github nick? I'll add you to the team.
>
> Mine is drnlm
Sent an invitation. Welcome on board!
Oleg.
--
Oleg Broytmanhttp://phdru.name/
On 1 December 2014 at 22:49, Oleg Broytman wrote:
>
>What's your Github nick? I'll add you to the team.
Mine is drnlm
--
Neil Muller
drnlmul...@gmail.com
I've got a gmail account. Why haven't I become cool?
--
Do
On Mon, Dec 01, 2014 at 02:58:20PM -0600, Ian Cordasco
wrote:
> >> Personally, I prefer working on GitHub if possible and I know the
> >> repository is already there. I would be happy to help coordinate and
> >> review pull requests there if people can help with this.
> >
> >What's your Githu
On Mon, Dec 1, 2014 at 2:47 PM, Oleg Broytman wrote:
> Hi!, Ian! Thank you!
>
You're welcome! I derive immense joy from seeing awesome projects make
the leap, so I'm really happy to see people enthusiastic about this.
> On Mon, Dec 01, 2014 at 08:53:34AM -0600, Ian Cordasco
> wrote:
>> Hey all
Hi!
On Mon, Dec 01, 2014 at 05:23:17PM +0200, Simon Cross
wrote:
> I'd also be interested in helping out.
Tell me your Github nick, I'll add you to the team.
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@phdru.name
Programmers don't die, they just GOS
Hi!
On Mon, Dec 01, 2014 at 05:15:52PM +0200, Neil Muller
wrote:
> On 1 December 2014 at 16:53, Ian Cordasco wrote:
> > Hey all,
> >
> > This is of course all predicated on the assumption that sqlobject's
> > dependencies support Python 3 as well, but I haven't looked into all
> > of them. It a
Hi!, Ian! Thank you!
On Mon, Dec 01, 2014 at 08:53:34AM -0600, Ian Cordasco
wrote:
> Hey all,
>
> I see there's been some discussion of late about porting the library
> to support Python 3. I'm a *very occasional* user of SQLObject and
> I've not contributed thus far, but I have some experience
I'd also be interested in helping out.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel
On 1 December 2014 at 16:53, Ian Cordasco wrote:
> Hey all,
>
> This is of course all predicated on the assumption that sqlobject's
> dependencies support Python 3 as well, but I haven't looked into all
> of them. It also is predicated on sqlobject wanting to wait (or not
> wait) for those depende
Hey all,
I see there's been some discussion of late about porting the library
to support Python 3. I'm a *very occasional* user of SQLObject and
I've not contributed thus far, but I have some experience porting
code-bases to support Python 3. The following is the sum of my
experiences and is by no
40 matches
Mail list logo
