forked from conda-forge/scrapy-feedstock
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.md
121 lines (85 loc) · 5.23 KB
/
README.md
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
<!--
# -*- mode: jinja -*-
-->
About scrapy
============
Home: https://scrapy.org/
Package license: BSD 3-Clauses
Feedstock license: BSD 3-Clause
Summary: A high-level Python Screen Scraping framework
Scrapy is an open source and collaborative framework for extracting the
data you need from websites in a fast, simple, yet extensible way.
Current build status
====================
[](https://circleci.com/gh/conda-forge/scrapy-feedstock)
[](https://travis-ci.org/conda-forge/scrapy-feedstock)
[](https://ci.appveyor.com/project/conda-forge/scrapy-feedstock/branch/master)
Current release info
====================
| Name | Downloads | Version | Platforms |
| --- | --- | --- | --- |
| [](https://anaconda.org/conda-forge/scrapy) | [](https://anaconda.org/conda-forge/scrapy) | [](https://anaconda.org/conda-forge/scrapy) | [](https://anaconda.org/conda-forge/scrapy) |
Installing scrapy
=================
Installing `scrapy` from the `conda-forge` channel can be achieved by adding `conda-forge` to your channels with:
```
conda config --add channels conda-forge
```
Once the `conda-forge` channel has been enabled, `scrapy` can be installed with:
```
conda install scrapy
```
It is possible to list all of the versions of `scrapy` available on your platform with:
```
conda search scrapy --channel conda-forge
```
About conda-forge
=================
[](http://numfocus.org)
conda-forge is a community-led conda channel of installable packages.
In order to provide high-quality builds, the process has been automated into the
conda-forge GitHub organization. The conda-forge organization contains one repository
for each of the installable packages. Such a repository is known as a *feedstock*.
A feedstock is made up of a conda recipe (the instructions on what and how to build
the package) and the necessary configurations for automatic building using freely
available continuous integration services. Thanks to the awesome service provided by
[CircleCI](https://circleci.com/), [AppVeyor](https://www.appveyor.com/)
and [TravisCI](https://travis-ci.org/) it is possible to build and upload installable
packages to the [conda-forge](https://anaconda.org/conda-forge)
[Anaconda-Cloud](https://anaconda.org/) channel for Linux, Windows and OSX respectively.
To manage the continuous integration and simplify feedstock maintenance
[conda-smithy](https://github.com/conda-forge/conda-smithy) has been developed.
Using the ``conda-forge.yml`` within this repository, it is possible to re-render all of
this feedstock's supporting files (e.g. the CI configuration files) with ``conda smithy rerender``.
For more information please check the [conda-forge documentation](https://conda-forge.org/docs/).
Terminology
===========
**feedstock** - the conda recipe (raw material), supporting scripts and CI configuration.
**conda-smithy** - the tool which helps orchestrate the feedstock.
Its primary use is in the construction of the CI ``.yml`` files
and simplify the management of *many* feedstocks.
**conda-forge** - the place where the feedstock and smithy live and work to
produce the finished article (built conda distributions)
Updating scrapy-feedstock
=========================
If you would like to improve the scrapy recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
`conda-forge` channel, whereupon the built conda packages will be available for
everybody to install and use from the `conda-forge` channel.
Note that all branches in the conda-forge/scrapy-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
* If the version of a package **is not** being increased, please add or increase
the [``build/number``](https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html#build-number-and-string).
* If the version of a package **is** being increased, please remember to return
the [``build/number``](https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html#build-number-and-string)
back to 0.
Feedstock Maintainers
=====================
* [@redapple](https://github.com/redapple/)
* [@rmax](https://github.com/rmax/)