Skip to content

Conversation

@TC-MO
Copy link
Contributor

@TC-MO TC-MO commented Jan 8, 2026

No description provided.

TC-MO added 2 commits January 8, 2026 17:17
fix capitalization of Actor
changes to formatting
streamlining prose
@TC-MO TC-MO self-assigned this Jan 8, 2026
@TC-MO TC-MO added documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team. labels Jan 8, 2026
@codecov
Copy link

codecov bot commented Jan 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.90%. Comparing base (ed35b6d) to head (190ca50).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #732      +/-   ##
==========================================
- Coverage   81.98%   81.90%   -0.08%     
==========================================
  Files          46       46              
  Lines        2681     2681              
==========================================
- Hits         2198     2196       -2     
- Misses        483      485       +2     
Flag Coverage Δ
integration 56.13% <ø> (ø)
unit 67.84% <ø> (-0.08%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@TC-MO TC-MO marked this pull request as ready for review January 9, 2026 09:12
@@ -0,0 +1,163 @@
---

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

General note:
Is it possible to move the overview page one level up, so that it is not in the Overview section? It's kinda weird UX-wise.
image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I was afraid that might happen. I think if we rename it to index.md it should not be separate openable section

Comment on lines +84 to +114
<Tabs>
<TabItem value="main.py" label="main.py" default>
<CodeBlock language="python">{
`from apify import Actor
${''}
async def main():
async with Actor:
Actor.log.info('Actor input:', await Actor.get_input())
await Actor.set_value('OUTPUT', 'Hello, world!')`
}</CodeBlock>
</TabItem>
<TabItem value="__main__.py" label="__main.py__">
<CodeBlock language="python">{
`import asyncio
import logging
${''}
from apify.log import ActorLogFormatter
${''}
from .main import main
${''}
handler = logging.StreamHandler()
handler.setFormatter(ActorLogFormatter())
${''}
apify_logger = logging.getLogger('apify')
apify_logger.setLevel(logging.DEBUG)
apify_logger.addHandler(handler)
${''}
asyncio.run(main())`
}</CodeBlock>
</TabItem>
</Tabs>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding some code comments?


### Creating Actors

To create and run Actors through Apify Console, refer to the [Console documentation](https://docs.apify.com/academy/getting-started/creating-actors#choose-your-template).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"through Apify Console"
Is through used in this context? I'd rather just use "in".

Suggested change
To create and run Actors through Apify Console, refer to the [Console documentation](https://docs.apify.com/academy/getting-started/creating-actors#choose-your-template).
To create and run Actors in Apify Console, refer to the [Console documentation](https://docs.apify.com/academy/getting-started/creating-actors#choose-your-template).


## Requirements

The Apify SDK requires Python version 3.8 or above to run Python Actors locally.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs previously said that the required version is 3.10 or above. Is this updated version correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I'll reach out and confirm the required version as client & sdk diverge here


## Adding dependencies

First, add them in the [`requirements.txt`](https://pip.pypa.io/en/stable/reference/requirements-file-format/) file in the Actor source folder.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
First, add them in the [`requirements.txt`](https://pip.pypa.io/en/stable/reference/requirements-file-format/) file in the Actor source folder.
First, add the dependencies in the [`requirements.txt`](https://pip.pypa.io/en/stable/reference/requirements-file-format/) file in the Actor source folder.

</TabItem>
</Tabs>

Then install the dependencies:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Then install the dependencies:
Finally, install the dependencies:

Copy link
Contributor

@vdusek vdusek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When running it locally, clicking "Docs" or "Get Started" redirects to
http://localhost:3000/sdk/python/docs/overview/introduction, which results in a 404.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants