profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/pawamoy/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Timothée Mazzucotelli pawamoy @sfeir France http://pawamoy.github.io/ I think I just like to create.

mkdocstrings/mkdocstrings 507

:blue_book: Automatic documentation from sources, for MkDocs.

pawamoy/aria2p 248

Command-line tool and library to interact with an aria2c daemon process with JSON-RPC.

mkdocstrings/pytkdocs 38

Load Python objects documentation.

pawamoy/copier-poetry 35

Copier template for Python projects managed by Poetry.

pawamoy/cookiecutter-awesome 24

Cookiecutter to create an awesome list.

pawamoy/dependenpy 18

Show the inter-dependencies between modules of Python packages.

pawamoy/awesome-repository 15

A curated list of services, tools and standards about (open source) repository management.

pawamoy/django-appsettings 13

Application settings helper for Django apps.

pawamoy/django-archan 9

A Django app that displays dependency matrices and other project architecture information

pawamoy/archan 8

Analysis of your architecture strength based on DSM data.

delete branch pawamoy/django-zxcvbn-password

delete branch : pyup-scheduled-update-2021-10-04

delete time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha 957f2ec9a041ce21ba1063f767e543c08658ebcd

Update sphinx-rtd-theme from 0.5.1 to 1.0.0

view details

push time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha cae137cb614f9589f07a60d4d8dfb92c561d9c6a

Update django from 3.1.7 to 3.2.8

view details

push time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha 19ad606c48e4a2465a9309f942a49ff0d2655609

Update sphinx from 3.5.3 to 4.2.0

view details

push time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha b0907dd0130218ad5dc24da4949a44f7ba82f064

Update pytest-django from 4.1.0 to 4.4.0

view details

push time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha ce3fb0381ab44f0b0dd59d815c8017c0da2653e9

Update pytest-cov from 2.11.1 to 3.0.0

view details

push time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha 851663c6fcf0a6c9aef1c35e6994b376d2504f04

Update pytest from 6.2.3 to 6.2.5

view details

push time in 4 days

push eventpawamoy/django-zxcvbn-password

pyup-bot

commit sha 4f9aba6a197a081fc1a9097d14fc467f86aed6f6

Update tox from 3.23.0 to 3.24.4

view details

push time in 4 days

issue commentmkdocstrings/mkdocstrings

Author's Website link returns 404

It seems the site URL is prefixed to the absolute URLs specified in the nav...

johnthagen

comment created time in 4 days

issue commentmkdocstrings/mkdocstrings

Author's Website link returns 404

Well no, still bugged :thinking:

johnthagen

comment created time in 4 days

issue commentmkdocstrings/mkdocstrings

Author's Website link returns 404

Thanks, I redeployed the docs, let see if this fixes it (it works when serving locally).

johnthagen

comment created time in 4 days

push eventmkdocstrings/mkdocstrings.github.io

Timothée Mazzucotelli

commit sha 08f2fc58c1c0ddc6e6430ac72fb0855b2d545f01

Deployed 1353e4d with MkDocs version: 1.2.3

view details

push time in 4 days

starteddbatten5/phylm

started time in 6 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

Also, maybe there' s a way to use line breaks in the syntax.

NOTE: Not a title. Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Nulla et euismod nulla. Curabitur feugiat, tortor non
consequat finibus, justo purus auctor massa, nec semper lorem quam in massa.
NOTE: **Title**  
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Nulla et euismod nulla. Curabitur feugiat, tortor non
consequat finibus, justo purus auctor massa, nec semper lorem quam in massa.
NOTE: Still a title?  
Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Nulla et euismod nulla. Curabitur feugiat, tortor non
consequat finibus, justo purus auctor massa, nec semper lorem quam in massa.

It degrades well, as the punctuation mark at the end of the title is not needed, and the line break is kept, degrading gracefully.

oprypin

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

Anyway I'm actually thinking more of the ** option. It even seems easiest to implement because the parsing is all done for free.

I'm curious, I think you have a good view on Python-Markdown: how would that be easier than parsing the solution with quotes instead, for example? Would you be able to know that the next "inline" (after the matched NOTE) is a bold-formatted sentence or something?

oprypin

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

Yes I guess you're right. Then yeah, without a punctuation mark at the end of the title, it doesn't degrade so well.

Another question: should the title be rendered as bold? That might be unwanted.

Pretty hard to find the right syntax :sweat_smile:

oprypin

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

Ah, I see. Why would the dot be undesired? A title is still a sentence, no?

oprypin

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

NOTE: This is used as the title. Stuff.

Well they'd notice it and fix it by including the dot in the **-delimited title. I don't think you should try do be smart here.

oprypin

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

It's true that with NOTE - Title: Contents you can't include : in the title. But any other solution would suffer from a similar issue: no double-quotes with Note "Title": Contents, or parentheses with Note (Title): Contents, unless you start counting opening and closing quotes/brackets, or add escaping support, etc.

I think that as long as the limitations are well documented, it*s fine :slightly_smiling_face:

oprypin

comment created time in 7 days

push eventpawamoy/griffe

Timothée Mazzucotelli

commit sha 0372acfae34b95156893c42dd6a17e447f9f3014

docs: Add itens to todo list

view details

Timothée Mazzucotelli

commit sha 5513ed5345db185e7c08890ca08de17932b34f51

refactor: Privatize stuff, fix loggers

view details

Timothée Mazzucotelli

commit sha d7cac7a1409d182a3d1a8fccdbe9f38cd7b61959

tests: Refactor tests helpers

view details

Timothée Mazzucotelli

commit sha 7bb221397f4750f4f4ef00236b3a18950b8616cd

chore: Add a profile task

view details

Timothée Mazzucotelli

commit sha 9b98da1ebd9c295e10cfb2beb75608c7f2d56103

chore: Always install async dep group

view details

Timothée Mazzucotelli

commit sha dedcd983c2a38372612ad62efe8697f1ed5e6120

chore: Upgrade black dev-dep

view details

Timothée Mazzucotelli

commit sha b2704833bc74131269306b9947ea2b46edafd349

feat: Add docstring section kinds

view details

Timothée Mazzucotelli

commit sha 9d3d0472d0bb55352b371de3da0816419fcf59e0

feat: Support more section kinds in Google-style

view details

Timothée Mazzucotelli

commit sha 8297b543d8ac31f2df2a14f77712739f8dbc6fc6

docs: Refine docstring

view details

Timothée Mazzucotelli

commit sha ad5b72d174433764e85f937ea1096c0f458532f8

feat: Add Numpy-style parser

view details

Timothée Mazzucotelli

commit sha 3d9465c9e0ab8ae580963c5adc8f1c4369ecb85a

chore: Remove verbose and debug flags in setup script

view details

Timothée Mazzucotelli

commit sha 21c99e0c0148e1dfc3d635d43918338a8e4cebe0

chore: Use postponed annotation in init

view details

Timothée Mazzucotelli

commit sha dfece1c0c73076c7d87d4df551f0994b4c2e3b69

refactor: Factorize function handling

view details

Timothée Mazzucotelli

commit sha cae85def4af1f67b537daabdb1e8ae9830dcaec7

refactor: Always set parent

view details

Timothée Mazzucotelli

commit sha 1442eba93479f24a4d90cd9b25f57d304a65cd6c

fix: Fix docstring getter

view details

Timothée Mazzucotelli

commit sha 5b2262f9cacce4044716661e6de49a1773ea3aa8

refactor: Improve annotation support

view details

Timothée Mazzucotelli

commit sha dce84d106cf067f11305f804a24cfd7d5643d902

feat: Support data (attributes/variables)

view details

Timothée Mazzucotelli

commit sha 56bf67a6886e5eb2d1743a6adfeecaf2c102befb

chore: Organize code with comments

view details

Timothée Mazzucotelli

commit sha 9805ed8e71a3cda852328797aeffdcf2861176a3

docs: Update TODO

view details

push time in 7 days

issue commentcopier-org/copier

feat: self-contained copier executable with Python in it

I've been able to bundle Python programs thanks to pyinstaller: https://github.com/pawamoy/aria2p/blob/3497d2b219bea4017644d384c1df08298f364689/duties.py#L90-L94

There are other projects that allow to do the same thing or similar.

heitorlessa

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

I prefer the parentheses as well over the quotes, but find them to de-emphasize the title, so it gave me another idea:

NOTE - This is used as the title: Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Nulla et euismod nulla. Curabitur feugiat, tortor non
consequat finibus, justo purus auctor massa, nec semper lorem quam in massa.
oprypin

comment created time in 7 days

issue commentoprypin/markdown-callouts

Allow arbitrary titles independent of the admonition class

The asterisks are already used in the original Markdown syntax

That's the point :smile: ! The goal is to be gracefully degraded to Markdown, and option 1 is the one that emphasizes the title the most, without visible characters around it in the final degraded HTML.

Consider the examples aboce rendered here on GitHub:

NOTE: This is used as the title. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla et euismod nulla. Curabitur feugiat, tortor non consequat finibus, justo purus auctor massa, nec semper lorem quam in massa.

NOTE "This is used as the title": Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla et euismod nulla. Curabitur feugiat, tortor non consequat finibus, justo purus auctor massa, nec semper lorem quam in massa.

oprypin

comment created time in 7 days

issue commentmkdocstrings/mkdocstrings

How to select only constants ?

Ah, I think we have to explicitly exclude the rest.

::: my_module
    selection:
      filters:
      - "!.*"
      - "^[A-Z][A-Z_0-9]*$"
remondn-swk

comment created time in 9 days

issue commentmkdocstrings/mkdocstrings

Is it possible to show the constant value ?

It's not currently possible, no. I'm working on something that will make it possible though. I can also accept PRs on pytkdocs :slightly_smiling_face:

remondn-swk

comment created time in 9 days

issue commentmkdocstrings/mkdocstrings

How to select only constants ?

Not sure if this is a typo in this post, but you have to apply filters on the parent object (here they're applied on CONST_1).

Try to exclude private methods/attributes instead:

::: my_module
    selection:
      filters: ["!^_"]

If there are other members you'd like to exclude, it would be safe to add their exact name to the filters as well:

::: my_module
    selection:
      filters: ["!^_", "!value"]

Alternatively, if all your constants are uppercase:

::: my_module
    selection:
      filters: ["^[A-Z][A-Z_0-9]*$"]
remondn-swk

comment created time in 9 days

pull request commentmkdocs/mkdocs

Uncomment build empty page test

https://stackoverflow.com/a/49718531/3451029

You can't mock the second argument of isinstance(), no. The documentation you found concerns making a mock as the first argument pass the test. If you want to produce something that is acceptable as the second argument to isinstance(), you actually have to have a type, not an instance (and mocks are always instances). You could use a subclass instead of MyClass instead

mondeja

comment created time in 11 days

issue commentmkdocstrings/mkdocstrings

Roadmap for mkdocstrings/pytkdocs in regard to extensions

There is no subprocess involved. Everything happens in the same python process.

I had to run it in a subprocess to support the live-reload feature of MkDocs. Otherwise modules are already loaded in sys.modules and docs are not refreshed. We can delete things manually from sys.modules, but it proved to be non-trivial (previous versions of mkdocstrings did that). However I didn't know about importlib.invalidate_caches(), so maybe this could help.

Building docs isn't a critical process

It is not indeed, but to support MkDocs live-reload while keeping a good UX, extracting docs should be fast. One or two seconds is acceptable for medium/big -sized projects. 22 seconds is not (it's the time it took when I ran pytkdocs against the whole Django code). The introspection is not really at fault here, all the time was wasted in inspect.getsource which reads files and tokenizes code again and again. There are possible optimizations to this of course, like parsing files ourselves ahead and keeping a record of the line numbers for each object. And we must parse every module anyway to find docstrings for attributes/variables (not doable through introspection). And we must also parse the import statements to be able to resolve names (not doable through introspection either). So as you can see, there are many things we need to do via manual parsing (well, more like visiting the AST) anyway :smile:

Due to python's dynamic nature, objects can be completely modified during runtime via metaclasses or decorators. When parsed statically from source code (and not being importing directly), I wonder how it's possible to know about such modifications

It's true, introspecting objects allows to see them as the users see them. Getting the same view with only AST is more difficult, and probably very hard in some cases (lots of dynamic indirections requiring lots of inference). But in general, I feel like this can be counter-balanced with good documentation. This metaclass completely changes that class? Reference metaclass from class' docs so the user knows what it does. Same for decorators. This variable is an instance of a class dynamically generated by function? Reference function in variable's doc. It's not as straight as with introspection though, I agree, and could be more difficult to read by users. They don't really care about how objects are internally created, but rather how to use them.

In my opinion, the ideal doc generating framework should natively support both approaches.

In the light of what we both shared above, this is a very interesting idea. I never considered of having both approaches in one tool. I'll have to think about that! Thank you very much for suggesting it :slightly_smiling_face:

mansenfranzen

comment created time in 11 days

push eventpawamoy/griffe

Timothée Mazzucotelli

commit sha 9c5978f1c4fe62885b9a638826f4eb82a5c9e7fa

Deployed ad5b72d with MkDocs version: 1.2.2

view details

push time in 11 days