%global _empty_manifest_terminate_build 0 Name: python-wefram Version: 0.2.54.post4 Release: 1 Summary: Wefram web platform License: MIT License URL: https://github.com/nf-it/wefram Source0: https://mirrors.nju.edu.cn/pypi/web/packages/5b/95/074b67b6efbb4afee23afc75507fd2cdfc241a4500f16ae9f45eab8ef856/wefram-0.2.54.post4.tar.gz BuildArch: noarch Requires: python3-aiofiles Requires: python3-aioredis Requires: python3-aiohttp Requires: python3-asyncpg Requires: python3-greenlet Requires: python3-itsdangerous Requires: python3-pillow Requires: python3-PyJWT Requires: python3-pytz Requires: python3-SQLAlchemy Requires: python3-starlette Requires: python3-starlette-context Requires: python3-uvicorn Requires: python3-uvloop Requires: python3-websockets Requires: python3-multipart Requires: python3-babel Requires: python3-jinja2 Requires: python3-csscompressor Requires: python3-jsmin Requires: python3-ldap3 Requires: python3-aiosmtplib %description **Wefram** is the open source platform used to create complex web projects consisting of both backend and frontend parts, allowing using both SSR (server-side rendering) using template renders, and CSR (client-side rendering) using *React* based SPA (single page application) approach. The main point is to handle as much as possible repeating or taking much of time elements of the development process by the platform (let's not name is "framework", okay?), giving programmers time to make end-point code of corresponding project applications only. The another goal of using Wefram is the ability of dividing the entire project into applications, often independent on each other. This provides us the posibility to write sometimes small, somethimes just funtion-resolving modules (applications) and store them in the repository, and re-use when needed. You may see many analogies with other module-based frameworks such as *Django* or *Flask*. But Wefram takes in work a lightly much, then those frameworks, providing already pre-developed, ready to use frontend SPA platform (React-based), and programmers of the project only focuses on the target functional code of the project modules, not wasting time on the frontend basics development, SSR & CSR integration into a single project, etc. %package -n python3-wefram Summary: Wefram web platform Provides: python-wefram BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-wefram **Wefram** is the open source platform used to create complex web projects consisting of both backend and frontend parts, allowing using both SSR (server-side rendering) using template renders, and CSR (client-side rendering) using *React* based SPA (single page application) approach. The main point is to handle as much as possible repeating or taking much of time elements of the development process by the platform (let's not name is "framework", okay?), giving programmers time to make end-point code of corresponding project applications only. The another goal of using Wefram is the ability of dividing the entire project into applications, often independent on each other. This provides us the posibility to write sometimes small, somethimes just funtion-resolving modules (applications) and store them in the repository, and re-use when needed. You may see many analogies with other module-based frameworks such as *Django* or *Flask*. But Wefram takes in work a lightly much, then those frameworks, providing already pre-developed, ready to use frontend SPA platform (React-based), and programmers of the project only focuses on the target functional code of the project modules, not wasting time on the frontend basics development, SSR & CSR integration into a single project, etc. %package help Summary: Development documents and examples for wefram Provides: python3-wefram-doc %description help **Wefram** is the open source platform used to create complex web projects consisting of both backend and frontend parts, allowing using both SSR (server-side rendering) using template renders, and CSR (client-side rendering) using *React* based SPA (single page application) approach. The main point is to handle as much as possible repeating or taking much of time elements of the development process by the platform (let's not name is "framework", okay?), giving programmers time to make end-point code of corresponding project applications only. The another goal of using Wefram is the ability of dividing the entire project into applications, often independent on each other. This provides us the posibility to write sometimes small, somethimes just funtion-resolving modules (applications) and store them in the repository, and re-use when needed. You may see many analogies with other module-based frameworks such as *Django* or *Flask*. But Wefram takes in work a lightly much, then those frameworks, providing already pre-developed, ready to use frontend SPA platform (React-based), and programmers of the project only focuses on the target functional code of the project modules, not wasting time on the frontend basics development, SSR & CSR integration into a single project, etc. %prep %autosetup -n wefram-0.2.54.post4 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-wefram -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri May 05 2023 Python_Bot - 0.2.54.post4-1 - Package Spec generated