2.10.5?

111 views
Skip to first unread message

Massimo DiPierro

unread,
May 3, 2015, 12:18:08 AM5/3/15
to web2py-d...@googlegroups.com
Do we still have pending issues with field.represent? I can take care them tomorrow.
Anything else before we release 2.10.5?


Paolo Valleri

unread,
May 3, 2015, 2:49:14 AM5/3/15
to web2py-d...@googlegroups.com
I'll fix https://github.com/web2py/pydal/issues/170 later today or tomorrow

Which version of pydal are you going to include in web2py 2.10.5 ? master or a new maintenance one?

 Paolo

2015-05-03 6:18 GMT+02:00 Massimo DiPierro <massimo....@gmail.com>:
Do we still have pending issues with field.represent? I can take care them tomorrow.
Anything else before we release 2.10.5?


--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details    : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official    : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Niphlod

unread,
May 3, 2015, 8:01:09 AM5/3/15
to web2py-d...@googlegroups.com
technically we can tag a 15.05

Paolo Valleri

unread,
May 3, 2015, 8:08:34 AM5/3/15
to web2py-d...@googlegroups.com
In that case, web2py 2.10.5 will bring few new features of pydal (iterRows, py3, mongo fix, basicStorage etc). 
Isn't 2.11 more appropriate? 

 Paolo

Niphlod

unread,
May 3, 2015, 8:11:25 AM5/3/15
to web2py-d...@googlegroups.com
are all of the above stable or experimental ?

Paolo Valleri

unread,
May 3, 2015, 8:18:09 AM5/3/15
to web2py-d...@googlegroups.com
who knows? I fixed all issues raised so far, that's all.
Syncing web2py to use the latest pydal is way to let other users to test it.
Surely, before 2.10.5 or 2.11 we need to publish beta

 Paolo

Niphlod

unread,
May 3, 2015, 8:26:38 AM5/3/15
to web2py-d...@googlegroups.com
who knows doesn't really answer the question. I get that "by design" something new isn't going to be stable, but at some point someone should take the responsibility of tagging it as such.

stable:
- documented
- tested
- doesn't expect to change its API

if all of the above are experimental, there's really no such need to release a "major" version of web2py.

BTW^3: I'm not a fan of pursuing backwards compatibility at all costs, but someone thought about app's code checking for
"old-style" classes (such as isinstance() calls) with the newer code ?

Massimo DiPierro

unread,
May 3, 2015, 8:31:05 AM5/3/15
to web2py-d...@googlegroups.com
I do not think we ever used old style classes anywhere

Massimo DiPierro

unread,
May 3, 2015, 8:31:20 AM5/3/15
to web2py-d...@googlegroups.com
Anyway. I agree 2.10.5 is this is all experimental.

On May 3, 2015, at 7:26 AM, Niphlod <nip...@gmail.com> wrote:

Niphlod

unread,
May 3, 2015, 8:38:00 AM5/3/15
to web2py-d...@googlegroups.com
app's code, not web2py (hopefully!)

I don't like to see users whining about "there's nothing in the CHANGELOG saying that what was "x" is now "y" " ..... let's don't make the same mistakes again.
Ok, technically the book doesn't say that module structure won't ever be changed, but this shouldn't allow us to change without even telling.

+1 for pushing releases but -1 on a sparse CHANGELOG that doesn't say anything technical for the fear of scaring newbies. e.g. " Rows can now be imported with from blablabla import Rows, rather than from pydal import Rows" is more helpful than "Rows is faster thanm 10X" .
Same concept applies to "iterrows" as a new feature : if it's experimental it should be clearly stated.

Niphlod

unread,
May 3, 2015, 8:39:31 AM5/3/15
to web2py-d...@googlegroups.com
also, please pull https://github.com/web2py/pydal/pull/171 in, so for the next tagged we'll have all tests passing.

Massimo DiPierro

unread,
May 3, 2015, 8:40:30 AM5/3/15
to web2py-d...@googlegroups.com
He we tested this does not break caching db().select(cache=(cache.disk,100)) and db().select(cache=(cache.disk,100),serializable=True)?

Niphlod

unread,
May 3, 2015, 8:58:19 AM5/3/15
to web2py-d...@googlegroups.com


On Sunday, May 3, 2015 at 2:40:30 PM UTC+2, Massimo Di Pierro wrote:
He we tested this does not break caching db().select(cache=(cache.disk,100)) and db().select(cache=(cache.disk,100),serializable=True)?

nobody added regressions tests for it (double-groan). I'll add them right now.
 

BTW: "at the end of the bug-squashing contest" there were ~150 issues. Now we're at ~160 (and I'm not counting pydal's). Something is clearly not going right on the "fixing issues" department...

Paolo Valleri

unread,
May 3, 2015, 9:37:44 AM5/3/15
to web2py-d...@googlegroups.com
I'm trying to add new tests every time I fix a bug. But tests are not always enough.
Consider iterselect has experimental but mind that iterparse and basicStorage impact to the whole pydal. iterparse due to the refactor of parse(), basicStorage because now is the super class of DAL,Table, Row. Given that, this is the reason because I suggest to release a beta.
In addition there is py3 in.

Regarding the issue, we should try to fix/close few of them.
Just for example, 12 are about GAE https://github.com/web2py/web2py/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+gae , personally I don't have an account on gae.

 Paolo

--

Giovanni Barillari

unread,
May 4, 2015, 7:19:41 PM5/4/15
to web2py-d...@googlegroups.com
I've just updated the next milestone of pyDAL to be 15.05 instead of 15.04, but I would prefer these steps:
1) craft a web2py 2.11 alpha or beta to selected users since we never tested py3 changes on existing py2 applications. These users should check if everything is ok with next pyDAL
2) select all the missing issues for pyDAL 15.05 and close 'em all before the 15th of May.
3) release pyDAL 15.05 on the 15th of May (or before if we're ready..)
4) if point 1 was ok, release web2py 2.11 stable with pyDAL 15.05

/Giovanni

Leonel Câmara

unread,
May 5, 2015, 3:14:24 PM5/5/15
to web2py-d...@googlegroups.com
I don't think we should release the next version without this being fixed

This is a backwards compatibility problem.

Niphlod

unread,
May 5, 2015, 3:27:16 PM5/5/15
to web2py-d...@googlegroups.com
uhm. that issue is open since 2012......... backward compatibility ?!

Leonel Câmara

unread,
May 5, 2015, 4:25:23 PM5/5/15
to web2py-d...@googlegroups.com
Well the example in the book is still wrong. You're right though I didn't notice the date.

Niphlod

unread,
May 5, 2015, 5:05:55 PM5/5/15
to web2py-d...@googlegroups.com
so maybe we should fix the book instead ?! :D
Reply all
Reply to author
Forward
0 new messages