On 09/30/2016 03:00 AM, Sylvia wrote:
Hi!
Thank you, Justin. I added a couple of things but I'm not the one to
write how to install Python or set a virtualenv. I only know how to
use some editors and IDE, Python was there when I started playing with
it... So maybe someone else should take that part and write it? Maybe
a screenshot too?
People from Python SIG looking at the article is a great idea! Thanks
for your feedback.
Cheers,
Sylvia
Hey Sylvia! Sorry for the delay in getting back to you here. Eduard
(x3mboy) volunteered to help cover some more pieces of getting started
in Fedora with Python. If it'll be alright, you two can be co-authors
for this piece when we ship it out.
I'd like to try to get this one in the schedule for the week of Oct. 17.
We'll check in again next week and see where we are on getting this one
published. We'll also check in with the Python SIG then too.
Thanks again for leading the writing on this one!
On Fri, 2016-09-30 at 00:11 -0400, Justin W. Flory wrote:
>
>
> Hey all! We also covered this article in today's meeting.
>
>> The article is well-organized and looking good. One thing that would
be
>> nice to have is some more details on setting up the environment
further
> with an editor and other useful tools for getting started in Python.
> Some things that might be helpful to cover here would be:
>
> (1) How to install Python (in case it was accidentally removed or
> missing for an unexpected purpose)
> (2) Searching for Python packages in Fedora
> (3) Setting up a Python virtualenv / editor environment (something
> specific that we could point users towards who want to get started
> writing Python code in Fedora)
>
>> We also thought we might get some members of the Python SIG to take
a
>> peek at this article before publishing since they might have a
vested
>> interest to make sure any cool, awesome tips that may not be obvious
are
> included in an article like this too. :)
>
>> Hope this feedback is helpful, Sylvia! Let us know if you need any
help
> or run into any blockers.
>
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com