A question on upgrading

[David Manns]

The docs suggest that to upgrade a source code installation (such as in development or on pythonanywhere as per the tutorial), now that everything is uv based, one should essentially start over from scratch.

This seems a bit onerous, to say the least.

Pre uv I would simply do a 'git pull' and possible "pip install --upgrade -r requirements.txt" and all was fine.

Is there an equivalent lightweight process?

Thanks

David

[Massimo]

It is indeed a different workflow but it not heaver. uv maintains it own cache of packages and will not reinstall things that have not changed. 

I have not tried but you should be able to generate a requirements.txt from the provided lock file:

https://github.com/astral-sh/uv/issues/6007#issuecomment-2303810114

[David Manns]

It would be nice to have a standard process for updating a development environment in vscode that gives a lightweight way to update master AND it's dependencies. I've seen different suggestions as to how to generate a requirements.txt file? Would running 'make assets' on the make any necessary changes to the venv after a git pull?

[David Manns]

for "on the make" please read "on the terminal"!

[Massimo DiPierro]

I will add a make option "make requirements"

You should never really need to use make assets. It is only used to build for publish to pypi

On Sun, Jun 1, 2025, 6:33 AM David Manns <dgm...@gmail.com> wrote:

for "on the make" please read "on the terminal"!

--
You received this message because you are subscribed to the Google Groups "py4web" group.
To unsubscribe from this group and stop receiving emails from it, send an email to py4web+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/py4web/317f5214-1d8f-4f3d-a24b-249bc15d5f6bn%40googlegroups.com.

[David Manns]

Sounds good.

I note that in the docs https://py4web.com/_documentation/static/en/chapter-03.html#setup-procedures 'Installing from source (globally)' calls for using 'make assets' and 'make test'.

[Massimo DiPierro]

Now that I think about it. It needs "make assets" in order to be able make new apps. Anyway, will review the instructions

To view this discussion visit https://groups.google.com/d/msgid/py4web/6ff70f89-429e-466a-8ae7-d12160a89f64n%40googlegroups.com.

[David Manns]

Another question is what is the most recent version of python supported. The docs simply state it needs python>=3.8. Wanting to make sure that potential users of my app don't run into problems with py4web installation, I created a new test account on pythonanywhere and installed py4web using the instructions for Installing from source (globally):

git clone https://github.com/web2py/py4web.git 

cd py4web 

make assets 

make test 

python -m pip install . 

py4web setup apps 

py4web set_password 

Pythonanywhere defaults new accounts to run using python 3.13

In make test there was an error, and 2 tests failed. I attach the recorded session (quite verbose as all the dynamic updates are recorded), stopped after 'make test'.

One can set the Pythonanywhere account to use different versions of python. I redid this using python 3.10 and it ran error free. I haven't tested with 3.11 or 3.12. What is officially supported?

[David Manns]

... I continued to complete the installation on 3.13 and installed my app. While I haven't tested exhaustively, it seems to be working fine in that environment, so perhaps the problems with 'make test' are not too significant?

David

[Nico Zanferrari]

Hi David,

the most recent version of python (3.13.4) is supported - and I think that no compatibility problem is known. Except the "make test", it seems ;-(

Nico

To view this discussion visit https://groups.google.com/d/msgid/py4web/ea073272-c631-48cd-aea8-3386293408bfn%40googlegroups.com.

[Nico Zanferrari]

Also, on my latest Ubuntu, and a venv Installing from source (locally), it seems I have no problem:

================================ tests coverage ================================
_______________ coverage: platform linux, python 3.13.3-final-0 ________________

Coverage HTML written to dir cov.html
============================= 27 passed in 27.02s ==============================

Looking at your session.txt, I see "OSError: [Errno 98] Address already in use" - maybe port 8001 was already in use?

Nico

[David Manns]

I think its quite possible that there was some kind of leftover process involved. Looks like there is no real problem, I will keep going with 3.13, time for a new venv on my development system.

David

[David Manns]

A couple of notes on "make requirements". I'm using it in my vscode development environment where I have py4web installed from source.

1) if requirements.txt already exists it says that requirements.txt is up to date. I had to delete requirements.txt and rerun make requirements to update the pydal requirement for the latest version.

2) it seems that the requirements.txt redundantly installed the latest release of py4web into my venv via pip install. I pip uninstall'ed it and everything is fine.

[Ali]

I'm a bit confused—does the following command no longer work for upgrading py4web? I believe I recently used it without any issues.

 python -m pip install --upgrade py4web --no-cache-dir

[Tom Clerckx]

The command you provided is OK.

Installing it via pip is the standard way of installing (and updating) py4web

As mentioned in the documentation, there are also other ways to install py4web (e.g. from source or from binaries)