Hi,
On 4/30/20 6:41 AM, Petr Viktorin wrote:
The draft lives on hackmd.io, which we found easy to collaborate with.
If you have an account there, we can add you. If you'd like to
collaborate some other way, let us know.
Please add mic...@michel-slm.name, thanks!
(I'm assuming hackmd.io allow
On Friday, 1 May 2020 15.57.36 WEST José Abílio Matos wrote:
> At the same I find it handy if a package is available at pypi to
be
> available as python3-.
Specially if the module can be used in other places...
--
José Abílio
___
python-devel mailing
On Friday, 1 May 2020 15.45.23 WEST Ian McInerney wrote:
> Thanks. I had seen that part of the policies, but I wasn't sure what counted
> as a "module" (I don't work with Python much and so I didn't know if the
> fact there were items installed into the site packages directory or an
> egg-info made
Thanks. I had seen that part of the policies, but I wasn't sure what
counted as a "module" (I don't work with Python much and so I didn't know
if the fact there were items installed into the site packages directory or
an egg-info made it count as a module).
-Ian
On Fri, May 1, 2020 at 3:30 PM Sco
On Fri, 1 May 2020, Ian McInerney wrote:
I am working on packaging up a git tool that is written in Python
(git-revise: https://github.com/mystor/git-revise), and was wondering if the
"python3-%{name}" applies to tools like this, e.g. ones that are written in
Python but are designed for use on t
I am working on packaging up a git tool that is written in Python
(git-revise: https://github.com/mystor/git-revise), and was wondering if
the "python3-%{name}" applies to tools like this, e.g. ones that are
written in Python but are designed for use on their own instead of as an
importable module