diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-django-shop.spec | 447 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 449 insertions, 0 deletions
@@ -0,0 +1 @@ +/django-shop-1.2.4.tar.gz diff --git a/python-django-shop.spec b/python-django-shop.spec new file mode 100644 index 0000000..65cd293 --- /dev/null +++ b/python-django-shop.spec @@ -0,0 +1,447 @@ +%global _empty_manifest_terminate_build 0 +Name: python-django-shop +Version: 1.2.4 +Release: 1 +Summary: A RESTful e-commerce framework based on Django +License: BSD License +URL: http://www.django-shop.org/ +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/73/da/c80e63ac1ed8ebacf10f83427f2689acece6e3cad554da826fcf5854a388/django-shop-1.2.4.tar.gz +BuildArch: noarch + +Requires: python3-Django +Requires: python3-django-filer +Requires: python3-django-ipware +Requires: python3-django-fsm +Requires: python3-django-fsm-admin +Requires: python3-djangorestframework +Requires: python3-django-rest-auth +Requires: python3-django-angular +Requires: python3-Django-Select2 +Requires: python3-django-admin-sortable2 +Requires: python3-django-formtools +Requires: python3-django-polymorphic +Requires: python3-django-post-office +Requires: python3-django-cms +Requires: python3-djangocms-cascade + +%description +# django-SHOP + +**Django-SHOP** aims to be a the easy, fun and fast e-commerce counterpart to +[django-CMS](https://www.django-cms.org/). + +[](https://travis-ci.org/awesto/django-shop?branch=master) +[](https://pypi.python.org/pypi/django-shop) +[](https://pypi.python.org/pypi/django-shop) +[](https://gitter.im/awesto/django-shop?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) +[](https://pypi.python.org/pypi/django-shop) +[](https://twitter.com/djangoSHOP) + +Here you can find the [full documentation for django-SHOP](https://django-shop.readthedocs.io/en/latest/). + +## Build the database model out of the product's properties – not vice versa + +Most e-commerce systems are shipped with a predefined database model for products. But products can +vary a lot, and it simply is impossible to create a model which fits for all of them. This is +esspecially true for products with a hierarchy of variants. In many popular e-commerce platforms, +you either have far too many attributes per product, and/or the really required attributes are +missing. + +In **django-SHOP** implementations, the product models reflect their pysical properties making it +possible to create complete and deep hierarchies of variations, but without having to fiddle with +unneeded properties. It furthermore avoids the need for an +[Entity Attribute Value Model](https://en.wikipedia.org/wiki/Entity–attribute–value_model), which +is considered a database anti-pattern, because it produces far too many table joins, when filtering +by property. + + +## Don't build pages using hard-coded templates – compose them + +With the advent of frameworks, such as Angular, React, Vue and Aurelia, building web-applications +shifted from a page-centric to a component-based approach. + +In **django-SHOP**, you are in full control over the page's layout, since all components are +encapsulated and independent from each other. This means that instead of adopting the Catalog, Cart, +Checkout and Order pages, use the **django-CMS** plugin system to compose everything required for +those pages. + + +## All Views are either HTML or RESTful services + +Browser based navigation is important, but nowadays it's only one of many channels clients use to +communicate with a web-server. Consider Single Page Applications or other native clients, where we +use RESTful APIs instead of pure HTTP. + +This substantially reduces the payload having to be transferred. It furthermore gives the client a +smoother user experience, since only the content has to be updated, rather than having to do full +page reloads. + + +## Programmable cart modifiers + +During checkout, taxes have to be applied or attributed. Depending on the shipping destination, the +product group and other factors, this computation can either be simple or quite demanding. +**Django-SHOP** offers a pluggable interface to create modifiers which calculate the cart's totals, +taxes and other costs. + +This same interface can be extended to compute the weight and shipping costs. It also can be used +for subtracting discounts or to add additional charges. + + +## Programmable workflow for fulfilment and delivery + +Fulfilling and shipping orders probably requires the most individual adaption for an e-commerce business. +**Django-SHOP** offers a programmable interface for order by using a finite +state machine to adopt the workflow. Each order may have several states, but the only actions +allowed are limited to explicitly defined state transitions. + + +## It's modular + +Whenever possible, extra features should be added by third party libraries. This implies that +**django-SHOP** aims to provide an API, which allows merchants to add every feature they desire. + +Currently there are third party libraries for several Payment Service Providers, such as +[PayPal](https://developer.paypal.com/docs/api/overview/), [Stripe](https://stripe.com/docs/api), +[BS-PayOne](https://www.bspayone.com/DE/en) and [Viveum](https://www.viveum.com/?lang=en). +An open interface allows you to add any other provider. + +Shipping Service Providers may be added as third party library as well. With +[SendCloud](https://docs.sendcloud.sc/), ship your orders using one or more parcel services +available for your region. + + +## Start by building your own demo + +Instead of providing an accessible online demo, **django-SHOP** can be set up in less than three +minutes and preconfigured to your needs. Having access to the product models, you can immediatly +start to play arround with, rename, and modify them to reflect the properties of your products. +This is the easiest way to get a shop up and running out of the box with the flexibility of a +website that you could have built from scratch. + +If you want to start with a fresh demo, please use the prepared +[Cookiecutter template for django-SHOP](https://github.com/awesto/cookiecutter-django-shop) +and follow the instructions. + + +## Audience of django-SHOP users + +Specifically, we aim at providing a clean, modular and Pythonic/Djangonic implementation of an +e-commerce framework, that a moderately experienced Django developer should be able to pick up +and run easily. Pure Django models are used to describe each product type, and so the Django admin +can be used to build a minimalistic editor for each of them. + + +## Consultancy + +We provide full consultancy support and are available for building complete e-commerce systems based +on **django-SHOP**. Please contact office@awesto.com for further questions. + + +## Documentation + +Read the full documentation on Read-the-docs: + +[https://django-shop.readthedocs.io/en/latest/](https://django-shop.readthedocs.io/en/latest/) + + + + +%package -n python3-django-shop +Summary: A RESTful e-commerce framework based on Django +Provides: python-django-shop +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-django-shop +# django-SHOP + +**Django-SHOP** aims to be a the easy, fun and fast e-commerce counterpart to +[django-CMS](https://www.django-cms.org/). + +[](https://travis-ci.org/awesto/django-shop?branch=master) +[](https://pypi.python.org/pypi/django-shop) +[](https://pypi.python.org/pypi/django-shop) +[](https://gitter.im/awesto/django-shop?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) +[](https://pypi.python.org/pypi/django-shop) +[](https://twitter.com/djangoSHOP) + +Here you can find the [full documentation for django-SHOP](https://django-shop.readthedocs.io/en/latest/). + +## Build the database model out of the product's properties – not vice versa + +Most e-commerce systems are shipped with a predefined database model for products. But products can +vary a lot, and it simply is impossible to create a model which fits for all of them. This is +esspecially true for products with a hierarchy of variants. In many popular e-commerce platforms, +you either have far too many attributes per product, and/or the really required attributes are +missing. + +In **django-SHOP** implementations, the product models reflect their pysical properties making it +possible to create complete and deep hierarchies of variations, but without having to fiddle with +unneeded properties. It furthermore avoids the need for an +[Entity Attribute Value Model](https://en.wikipedia.org/wiki/Entity–attribute–value_model), which +is considered a database anti-pattern, because it produces far too many table joins, when filtering +by property. + + +## Don't build pages using hard-coded templates – compose them + +With the advent of frameworks, such as Angular, React, Vue and Aurelia, building web-applications +shifted from a page-centric to a component-based approach. + +In **django-SHOP**, you are in full control over the page's layout, since all components are +encapsulated and independent from each other. This means that instead of adopting the Catalog, Cart, +Checkout and Order pages, use the **django-CMS** plugin system to compose everything required for +those pages. + + +## All Views are either HTML or RESTful services + +Browser based navigation is important, but nowadays it's only one of many channels clients use to +communicate with a web-server. Consider Single Page Applications or other native clients, where we +use RESTful APIs instead of pure HTTP. + +This substantially reduces the payload having to be transferred. It furthermore gives the client a +smoother user experience, since only the content has to be updated, rather than having to do full +page reloads. + + +## Programmable cart modifiers + +During checkout, taxes have to be applied or attributed. Depending on the shipping destination, the +product group and other factors, this computation can either be simple or quite demanding. +**Django-SHOP** offers a pluggable interface to create modifiers which calculate the cart's totals, +taxes and other costs. + +This same interface can be extended to compute the weight and shipping costs. It also can be used +for subtracting discounts or to add additional charges. + + +## Programmable workflow for fulfilment and delivery + +Fulfilling and shipping orders probably requires the most individual adaption for an e-commerce business. +**Django-SHOP** offers a programmable interface for order by using a finite +state machine to adopt the workflow. Each order may have several states, but the only actions +allowed are limited to explicitly defined state transitions. + + +## It's modular + +Whenever possible, extra features should be added by third party libraries. This implies that +**django-SHOP** aims to provide an API, which allows merchants to add every feature they desire. + +Currently there are third party libraries for several Payment Service Providers, such as +[PayPal](https://developer.paypal.com/docs/api/overview/), [Stripe](https://stripe.com/docs/api), +[BS-PayOne](https://www.bspayone.com/DE/en) and [Viveum](https://www.viveum.com/?lang=en). +An open interface allows you to add any other provider. + +Shipping Service Providers may be added as third party library as well. With +[SendCloud](https://docs.sendcloud.sc/), ship your orders using one or more parcel services +available for your region. + + +## Start by building your own demo + +Instead of providing an accessible online demo, **django-SHOP** can be set up in less than three +minutes and preconfigured to your needs. Having access to the product models, you can immediatly +start to play arround with, rename, and modify them to reflect the properties of your products. +This is the easiest way to get a shop up and running out of the box with the flexibility of a +website that you could have built from scratch. + +If you want to start with a fresh demo, please use the prepared +[Cookiecutter template for django-SHOP](https://github.com/awesto/cookiecutter-django-shop) +and follow the instructions. + + +## Audience of django-SHOP users + +Specifically, we aim at providing a clean, modular and Pythonic/Djangonic implementation of an +e-commerce framework, that a moderately experienced Django developer should be able to pick up +and run easily. Pure Django models are used to describe each product type, and so the Django admin +can be used to build a minimalistic editor for each of them. + + +## Consultancy + +We provide full consultancy support and are available for building complete e-commerce systems based +on **django-SHOP**. Please contact office@awesto.com for further questions. + + +## Documentation + +Read the full documentation on Read-the-docs: + +[https://django-shop.readthedocs.io/en/latest/](https://django-shop.readthedocs.io/en/latest/) + + + + +%package help +Summary: Development documents and examples for django-shop +Provides: python3-django-shop-doc +%description help +# django-SHOP + +**Django-SHOP** aims to be a the easy, fun and fast e-commerce counterpart to +[django-CMS](https://www.django-cms.org/). + +[](https://travis-ci.org/awesto/django-shop?branch=master) +[](https://pypi.python.org/pypi/django-shop) +[](https://pypi.python.org/pypi/django-shop) +[](https://gitter.im/awesto/django-shop?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) +[](https://pypi.python.org/pypi/django-shop) +[](https://twitter.com/djangoSHOP) + +Here you can find the [full documentation for django-SHOP](https://django-shop.readthedocs.io/en/latest/). + +## Build the database model out of the product's properties – not vice versa + +Most e-commerce systems are shipped with a predefined database model for products. But products can +vary a lot, and it simply is impossible to create a model which fits for all of them. This is +esspecially true for products with a hierarchy of variants. In many popular e-commerce platforms, +you either have far too many attributes per product, and/or the really required attributes are +missing. + +In **django-SHOP** implementations, the product models reflect their pysical properties making it +possible to create complete and deep hierarchies of variations, but without having to fiddle with +unneeded properties. It furthermore avoids the need for an +[Entity Attribute Value Model](https://en.wikipedia.org/wiki/Entity–attribute–value_model), which +is considered a database anti-pattern, because it produces far too many table joins, when filtering +by property. + + +## Don't build pages using hard-coded templates – compose them + +With the advent of frameworks, such as Angular, React, Vue and Aurelia, building web-applications +shifted from a page-centric to a component-based approach. + +In **django-SHOP**, you are in full control over the page's layout, since all components are +encapsulated and independent from each other. This means that instead of adopting the Catalog, Cart, +Checkout and Order pages, use the **django-CMS** plugin system to compose everything required for +those pages. + + +## All Views are either HTML or RESTful services + +Browser based navigation is important, but nowadays it's only one of many channels clients use to +communicate with a web-server. Consider Single Page Applications or other native clients, where we +use RESTful APIs instead of pure HTTP. + +This substantially reduces the payload having to be transferred. It furthermore gives the client a +smoother user experience, since only the content has to be updated, rather than having to do full +page reloads. + + +## Programmable cart modifiers + +During checkout, taxes have to be applied or attributed. Depending on the shipping destination, the +product group and other factors, this computation can either be simple or quite demanding. +**Django-SHOP** offers a pluggable interface to create modifiers which calculate the cart's totals, +taxes and other costs. + +This same interface can be extended to compute the weight and shipping costs. It also can be used +for subtracting discounts or to add additional charges. + + +## Programmable workflow for fulfilment and delivery + +Fulfilling and shipping orders probably requires the most individual adaption for an e-commerce business. +**Django-SHOP** offers a programmable interface for order by using a finite +state machine to adopt the workflow. Each order may have several states, but the only actions +allowed are limited to explicitly defined state transitions. + + +## It's modular + +Whenever possible, extra features should be added by third party libraries. This implies that +**django-SHOP** aims to provide an API, which allows merchants to add every feature they desire. + +Currently there are third party libraries for several Payment Service Providers, such as +[PayPal](https://developer.paypal.com/docs/api/overview/), [Stripe](https://stripe.com/docs/api), +[BS-PayOne](https://www.bspayone.com/DE/en) and [Viveum](https://www.viveum.com/?lang=en). +An open interface allows you to add any other provider. + +Shipping Service Providers may be added as third party library as well. With +[SendCloud](https://docs.sendcloud.sc/), ship your orders using one or more parcel services +available for your region. + + +## Start by building your own demo + +Instead of providing an accessible online demo, **django-SHOP** can be set up in less than three +minutes and preconfigured to your needs. Having access to the product models, you can immediatly +start to play arround with, rename, and modify them to reflect the properties of your products. +This is the easiest way to get a shop up and running out of the box with the flexibility of a +website that you could have built from scratch. + +If you want to start with a fresh demo, please use the prepared +[Cookiecutter template for django-SHOP](https://github.com/awesto/cookiecutter-django-shop) +and follow the instructions. + + +## Audience of django-SHOP users + +Specifically, we aim at providing a clean, modular and Pythonic/Djangonic implementation of an +e-commerce framework, that a moderately experienced Django developer should be able to pick up +and run easily. Pure Django models are used to describe each product type, and so the Django admin +can be used to build a minimalistic editor for each of them. + + +## Consultancy + +We provide full consultancy support and are available for building complete e-commerce systems based +on **django-SHOP**. Please contact office@awesto.com for further questions. + + +## Documentation + +Read the full documentation on Read-the-docs: + +[https://django-shop.readthedocs.io/en/latest/](https://django-shop.readthedocs.io/en/latest/) + + + + +%prep +%autosetup -n django-shop-1.2.4 + +%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-django-shop -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.2.4-1 +- Package Spec generated @@ -0,0 +1 @@ +fa248dc21bf5237079d65ca8b3fe1f03 django-shop-1.2.4.tar.gz |