Should we expect any changes in scrapinghub cloud? Any default deploy settings (like change from scrapy:1.3-py2 to scrapy:1.3-py3) or maybe something more serious?
Best Answer
n
nestor
said
over 5 years ago
Nothing set in stone yet. Probably Py3 stacks will be the default stack, however we will most likely continue to support 2.7 for backwards compatibility until everyone has moved to Py3.
1 Comment
nestor
said
over 5 years ago
Answer
Nothing set in stone yet. Probably Py3 stacks will be the default stack, however we will most likely continue to support 2.7 for backwards compatibility until everyone has moved to Py3.
Lukasz Jaworowski
Hi,
Python 2.7 is reaching its end of life on 1st Jan, 2020 as mentioned by https://legacy.python.org/dev/peps/pep-0373/ .
Should we expect any changes in scrapinghub cloud? Any default deploy settings (like change from scrapy:1.3-py2 to scrapy:1.3-py3) or maybe something more serious?
Nothing set in stone yet. Probably Py3 stacks will be the default stack, however we will most likely continue to support 2.7 for backwards compatibility until everyone has moved to Py3.
nestor
Nothing set in stone yet. Probably Py3 stacks will be the default stack, however we will most likely continue to support 2.7 for backwards compatibility until everyone has moved to Py3.
-
Unable to select Scrapy project in GitHub
-
ScrapyCloud can't call spider?
-
Unhandled error in Deferred
-
Item API - Filtering
-
newbie to web scraping but need data from zillow
-
ValueError: Invalid control character
-
Cancelling account
-
Best Practices
-
Beautifulsoup with ScrapingHub
-
Delete a project in ScrapingHub
See all 458 topics