[future] web2py weppy and web3py

[Giovanni Barillari]

Hi all and happy Halloween!

Today I've just released weppy 0.8, and this will be the last release before a major refactoring on a large part of its codebase and that will be the 1.0

Planning the refactoring, I'm considering splitting weppy in multiple packages and considering that some parts will still be in common (or similar) to web2py and web3py,

it would be nice to do that so both web2py and web3py can use those modules, and all the three frameworks can take advantage of having the same code base (which means more developers, more code quality, sharing new features).

Some example right now can be:

- templates engine

- translator

- the migration engine for pydal (http://weppy.org/docs/latest/dal/migrations)

- forms (on web3py at least)

Let me know what you guys think, right now is just an idea!

/Giovanni

[Paolo Valleri]

Given the good outcomes of pydal, I agree in following the same path for other core components (scheduler too).

Paolo

[Richard Vézina]

I hope, I will not exacerbate to much sensitivity... I really appreciate contributions of everyone... I am in favor of anything that could improve web2py, but there is something I feel we will lost at some point. I mean web2py is a fullstack, and we kind of propose to split it appart to improve contribution... To my knowledge there is already many template engine, for forms there is WTForms, dal (sqlalchemy is not the same kind of beast), than ligth framework that let you pull everything together (Flask, Bottle, etc) exist. So, why try to dismantle web2py, instead of just use the already existing components... For sure we can improve web2py a lot by decoupling many of it component, but at the same time we are stock with the actual state (no offense there was a lot of progress lately) since almost 2 years because we don't agree on which path to take to get foward...

IMHO, web2py has less traction than others frameworks (let say Django) because it happen later, and because for provide all it goodies there is design decisions that been made that are not embraced by purist... Also, web2py users base is less likely to contribute because they are buzy developping there app and are less techy than other community members. So, I am not sure we should count over more contributors if we are splitting web2py appart...

On the other hand, I think that if we were offering python 3 support (I think we are near of it) and make few incremental improvements we could grab some more users that just pass their way because we don't support python 3. We had improved testing. We should stay focused for python 3, if we are not there yet and don't need to broke backward compatibility to get it done.

Then, I am open to anything, I ma just not convienced that spending efforts over splitting web2py could bring more developpers, but as long as doing it don't break web2py way of working I am not closed to the idea, but I don't see this as great improvement of web2py as it will take a lot of efforts to just split thing off to put them together differently and making sure nothing get broken. If it makes things easier later to improve web2py it a great thing though. 

So I suggest that we identify which part being decoupled would benefit web2py/web3py the most... Hack it, then get back and set another goal, but to me the goal/priority should be get to web3py the sooner.

I think web2py is what glue us together.

:D

Thanks

Richard

--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-developers@googlegroups.com
unsubscribe: web2py-developers+unsubscribe@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-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Giovanni Barillari]

@Richard

you probably misunderstood, I was talking about splitting weppy in components and re-use them inside web2py/web3py to unify parts of the code-base.

Notice that all the codebase of weppy is python 3 compatible since the end of the last year.

/Giovanni

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.

[Richard Vézina]

My bads than...

:)

make speech: web2py-developers@googlegroups.com
unsubscribe: web2py-developers+unsubscribe@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-developers+unsubscribe@googlegroups.com.

[Anthony]

+1

[Michele Comitini]

Thanks to Giovanni that handled pydal "componentization" very well.  

The packaging of web2py has been very smooth and now the codebase is much more stable and easier to test.

I see more pros than cons in having different frameworks sharing common parts even considering the integration effort.

+1

 

--

[Massimo DiPierro]

i agree except web2py forms should be deprecated in favor of new logic

--

[Giovanni Barillari]

It would be awesome if we can have web2py as a pip package so we can use dependencies in a more common way and avoid patching sys.path...

/Giovanni

Il giorno martedì 1 novembre 2016 20:20:39 UTC+1, Massimo Di Pierro ha scritto:

i agree except web2py forms should be deprecated in favor of new logic

On Oct 31, 2016 14:21, "Giovanni Barillari" <giovanni....@gmail.com> wrote:

Hi all and happy Halloween!

Today I've just released weppy 0.8, and this will be the last release before a major refactoring on a large part of its codebase and that will be the 1.0

Planning the refactoring, I'm considering splitting weppy in multiple packages and considering that some parts will still be in common (or similar) to web2py and web3py,

it would be nice to do that so both web2py and web3py can use those modules, and all the three frameworks can take advantage of having the same code base (which means more developers, more code quality, sharing new features).

Some example right now can be:

- templates engine

- translator

- the migration engine for pydal (http://weppy.org/docs/latest/dal/migrations)

- forms (on web3py at least)

Let me know what you guys think, right now is just an idea!

/Giovanni

--
-- 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.

[Niphlod]

we made definitely steps towards the achievement but we still miss a proper path to separate the usual "all included" web2py from a proper "standard" package.