You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -111,7 +111,13 @@ Apart of improving the situation for frozenapp/zipapp use cases this brings thes
111
111
1) Reduction of total complexity (cyclomatic complexity goes from 18329 to 18307 a delta of 22, number of lines from 58033 to 57967, a delta of 134)
112
112
2) The ```pythonpathsetter``` feature is not advertised. It is likely that its most common use is in Robot Framework quality control.
113
113
- if that would make testing easier/faster for multiple python installations that might be worth the risk.
114
-
- solutions like [uvx](https://docs.astral.sh/uv/)```uvx --python 3.14 --from . --reinstall robot``` are available, taking care of warehousing the python versions
114
+
- solutions like [uvx](https://docs.astral.sh/uv/)```uvx --python 3.14 --from . --reinstall robot``` are available, taking care of warehousing the python versions.
115
+
- Virutal environments are cheap, get two.
116
+
- Have you heard of ziapps? You can have the Robot Framework version you like installed into a single file, and then use the python of choice to execute it!
117
+
- Have you heard of frozen apps? You can have Robot Framework with python frozen together ahead of time!
118
+
3) The fact that Robot Framework "script edition" ignores installed Robot Framework but requires to be part of the Robot Framework source tree
119
+
are two unusual properties, which can cause confusion.
120
+
115
121
It is hard to get this point across, but the "unpack into a directory" distribution method is very much outdated by now.
116
122
117
123
#### do not modify the ```sys.path``` (would need to come from upstream)
0 commit comments