web2py 1.75.1 is Out

9 views
Skip to first unread message

mdipierro

unread,
Feb 12, 2010, 5:24:06 PM2/12/10
to web2py-users
Please check it out. Minor fixes.

Alexandre Andrade

unread,
Feb 12, 2010, 7:52:46 PM2/12/10
to web...@googlegroups.com
If minor fixes, why 1.15.1 and not 1.74.12?

Between the fixes, is the one about change/personalize auth tables?

2010/2/12, mdipierro <mdip...@cs.depaul.edu>:


> Please check it out. Minor fixes.
>

> --
> You received this message because you are subscribed to the Google Groups
> "web2py-users" group.
> To post to this group, send email to web...@googlegroups.com.
> To unsubscribe from this group, send email to
> web2py+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/web2py?hl=en.
>
>


--
Atenciosamente

--
=========================
Alexandre Andrade
Hipercenter.com

mdipierro

unread,
Feb 12, 2010, 10:06:35 PM2/12/10
to web2py-users
If this something you sent me? I do not recall anything on the
subject.

On Feb 12, 6:52 pm, Alexandre Andrade <alexandrema...@gmail.com>
wrote:


> If minor fixes, why 1.15.1 and not 1.74.12?
>
> Between the fixes, is the one about change/personalize auth tables?
>

> 2010/2/12, mdipierro <mdipie...@cs.depaul.edu>:

Jonathan Lundell

unread,
Feb 12, 2010, 10:35:11 PM2/12/10
to web...@googlegroups.com
On Feb 12, 2010, at 7:06 PM, mdipierro wrote:

> If this something you sent me? I do not recall anything on the
> subject.

The question is: how did you decide to go from 1.74 to 1.75, instead of bumping the third field.

mdipierro

unread,
Feb 12, 2010, 11:02:41 PM2/12/10
to web2py-users
Normally we bump because there is a new feature, not a bug fix.
Technically no features was added in 1.75.1 vs 1.74.11 but many new
features have been added in between 1.74.1 and 1.74.11. All together
they have been tested and together they justify a new full version
number. I think they jump should have been happened before but i did
not feel confident. I agree this process is somewhat arbitrary. I
would not oppose to some more strict rules about numbering. Feel free
to make a proposal.

Thadeus Burgess

unread,
Feb 12, 2010, 11:04:55 PM2/12/10
to web...@googlegroups.com
Looking at the commit logs here is the following.

Bug fixes.

Reserved SQL keywords checking

Parents and siblings

Can specify port with Firebird

Upgrade an app by unpacking over it

-Thadeus

Jonathan Lundell

unread,
Feb 12, 2010, 11:12:03 PM2/12/10
to web...@googlegroups.com
On Feb 12, 2010, at 8:02 PM, mdipierro wrote:

> Normally we bump because there is a new feature, not a bug fix.
> Technically no features was added in 1.75.1 vs 1.74.11 but many new
> features have been added in between 1.74.1 and 1.74.11. All together
> they have been tested and together they justify a new full version
> number. I think they jump should have been happened before but i did
> not feel confident. I agree this process is somewhat arbitrary. I
> would not oppose to some more strict rules about numbering. Feel free
> to make a proposal.

Nothing from me. In my (commercial) experience it tends to be a marketing decision. But that it's always a good conversation starter.

(What would it take to go from 1. to 2.? Presumably less than it would take to go from web2py to web3py.)

Thadeus Burgess

unread,
Feb 12, 2010, 11:19:07 PM2/12/10
to web...@googlegroups.com
wow... web4py web5py...

When will software stop being about versions and just being about
feature sets and stability!

-Thadeus

Wes James

unread,
Feb 13, 2010, 12:10:45 AM2/13/10
to web...@googlegroups.com
On Fri, Feb 12, 2010 at 9:12 PM, Jonathan Lundell <jlun...@pobox.com> wrote:
> On Feb 12, 2010, at 8:02 PM, mdipierro wrote:

<snip>

> (What would it take to go from 1. to 2.? Presumably less than it would take to go from web2py to web3py.)

Maybe you already know, but the 2 in web2py refers to the python major
version it is supported for. When it moves to full support for python
3 it will be web3py.

Regarding version numbers, I like just the date it was released.
i.e., Version 20100212 instead of 1.75.1 :)

-wes

mdipierro

unread,
Feb 13, 2010, 12:25:44 AM2/13/10
to web2py-users
web-to-py(thon)
web-2(.0)-py(thon)
web-(python)2-py(thon)

when/if there will be a web3py 3 will definitively mean python 3.
Right now I am not so excited about python 3. Perhaps a web4py is more
likely although py4web would be a better name.

On Feb 12, 11:10 pm, Wes James <compte...@gmail.com> wrote:

Alexandre Andrade

unread,
Feb 13, 2010, 5:09:25 AM2/13/10
to web...@googlegroups.com
In 8/Feb/2010 you wrote about the subject "Customizing Auth"
------------------------------------
It is combinations of two things:
1) a bug (just fixed in trunk)
2) the example is missing something (I fixed it). Should be:

auth.settings.table_user = db.define_table('auth_user',
   Field('first_name', length=512,default=''),
   Field('last_name', length=512,default=''),
   Field('email', length=512,default='',
         requires = [IS_EMAIL(),IS_NOT_IN_DB(db,'
auth_user.email')]),
   Field('password', 'password',
         readable=False, label='Password',
         requires=CRYPT(auth.settings.hmac_key)),
   Field('registration_key', length=512,
         writable=False, readable=False,default=''),
   Field('reset_password_key', length=512,
         writable=False, readable=False, default=''))

Sorry about this and thanks for help in debugging.

Massimo
-------------------------------------------------------

I'm asking about the 1) a bug fixed in trunck



2010/2/13 mdipierro <mdip...@cs.depaul.edu>

mdipierro

unread,
Feb 13, 2010, 10:41:39 AM2/13/10
to web2py-users
I do not remember what it was but if I said it was fixed it should be
fixed. Are you still having problems?

On Feb 13, 4:09 am, Alexandre Andrade <alexandrema...@gmail.com>
wrote:


> In 8/Feb/2010 you wrote about the subject "Customizing Auth"
> ------------------------------------
> It is combinations of two things:
> 1) a bug (just fixed in trunk)
> 2) the example is missing something (I fixed it). Should be:
>
> auth.settings.table_user = db.define_table('auth_user',
>     Field('first_name', length=512,default=''),
>    Field('last_name', length=512,default=''),
>    Field('email', length=512,default='',
>           requires = [IS_EMAIL(),IS_NOT_IN_DB(db,'
> auth_user.email')]),
>     Field('password', 'password',
>          readable=False, label='Password',
>           requires=CRYPT(auth.settings.hmac_key)),
>     Field('registration_key', length=512,
>           writable=False, readable=False,default=''),
>    Field('reset_password_key', length=512,
>           writable=False, readable=False, default=''))
>
> Sorry about this and thanks for help in debugging.
>
> Massimo
> -------------------------------------------------------
>
> I'm asking about the 1) a bug fixed in trunck
>

> 2010/2/13 mdipierro <mdipie...@cs.depaul.edu>


>
>
>
> > If this something you sent me? I do not recall anything on the
> > subject.
>
> > On Feb 12, 6:52 pm, Alexandre Andrade <alexandrema...@gmail.com>
> > wrote:
> > > If minor fixes, why 1.15.1 and not 1.74.12?
>
> > > Between the fixes, is the one about change/personalize auth tables?
>
> > > 2010/2/12, mdipierro <mdipie...@cs.depaul.edu>:
>
> > > > Please check it out. Minor fixes.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "web2py-users" group.
> > > > To post to this group, send email to web...@googlegroups.com.
> > > > To unsubscribe from this group, send email to

> > > > web2py+un...@googlegroups.com<web2py%2Bunsu...@googlegroups.com>


> > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/web2py?hl=en.
>
> > > --
> > > Atenciosamente
>
> > > --
> > > =========================
> > > Alexandre Andrade
> > > Hipercenter.com
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "web2py-users" group.
> > To post to this group, send email to web...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > web2py+un...@googlegroups.com<web2py%2Bunsu...@googlegroups.com>

Beerc

unread,
Feb 15, 2010, 9:19:12 AM2/15/10
to web2py-users
I suggest semantic versioning (http://semver.org/).

mdipierro

unread,
Feb 15, 2010, 10:33:28 AM2/15/10
to web2py-users
I think the intent was to follow that already. The only issue is that
sometimes a new feature is added but we want to wait that people test
it until the version number is incremented. People do not really seem
to test code in trunk.

Thadeus Burgess

unread,
Feb 15, 2010, 10:49:16 AM2/15/10
to web...@googlegroups.com
I test code in trunk with my development, I always pull changes at the
start of my day.

On the server however... I havn't upgraded those things in forever,
and I won't until I find a version I am happy with :)

-Thadeus

mdipierro

unread,
Feb 15, 2010, 11:12:12 AM2/15/10
to web2py-users
Good to know. Yet people who run windows for example, they usually
wait for the executable.

On Feb 15, 9:49 am, Thadeus Burgess <thade...@thadeusb.com> wrote:
> I test code in trunk with my development, I always pull changes at the
> start of my day.
>
> On the server however... I havn't upgraded those things in forever,
> and I won't until I find a version I am happy with :)
>
> -Thadeus
>

Reply all
Reply to author
Forward
0 new messages