From ed at pythoncharmers.com Fri Sep 1 03:21:58 2017
From: ed at pythoncharmers.com (Ed Schofield)
Date: Fri, 1 Sep 2017 09:21:58 +0200
Subject: [melbourne-pug] Next Melbourne Python meeting - Monday 4 September
Message-ID: <5390CE1B-4100-4132-84DC-7C5E2E66EE44@pythoncharmers.com>
Hi everyone!
Our next meeting of the Melbourne Python users group will be on Monday 4 September. We have two great talks planned:
1. Linus Chang: Updates on ScramFS (45 minutes)
Linus will share his team's experiences building "the world's most advanced cryptographic file system, built in Python". Topics include:
Meeting legal regulations around encryption, privacy, data breaches. Examples of ScramFS: CLI, API, Fuse mount, and GUI.
Overview of cloud filesystems and their limitations: Google Drive, Microsoft One Drive, Dropbox. Attacking a filesystem.
Encoding binary data as text: an overview of base64, uuencode, and alternatives suitable for encoding filenames
How to implement an encrypted key-value store in 10 minutes flat
2. Ned Letcher: Reactive web visualizations with Python (20 minutes)
Ned will give an overview of making dashboards and other interactive data-oriented web interfaces using Dash, an open source library recently released by Plotly. He will also share his experiences with deploying Dash apps on AWS (and perhaps zappa.io).
Where:
Outcome-Hub Co-Working Space
Suite 1, 121 Cardigan Street, Carlton
When: 5.45pm for mingling; talks starting at 6pm
Afterwards: general announcements and pizza. Then maybe drinks on Lygon Street?
Sponsorship: many thanks to Outcome Hub for providing the venue and Python Charmers for ongoing sponsorship of Meetup fees
I'll still be overseas, but a big thanks to Sam (CCed) for hosting!
Best wishes,
Ed
--
Dr. Edward Schofield
Python Charmers
+61 (0)405 676 229
http://pythoncharmers.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From brian at linuxpenguins.xyz Wed Sep 6 01:43:18 2017
From: brian at linuxpenguins.xyz (Brian May)
Date: Wed, 06 Sep 2017 15:43:18 +1000
Subject: [melbourne-pug] Django: Automatically creating default groups and
assigning default permissions
Message-ID: <0279685e3d84528f8d960127d9b08ff0@linuxpenguins.xyz>
Hello,
Just wondering how to create groups automatically in Django and
automatically assign permissions?
Sounds easy. I have created a database migration to do just this.
The problem is under Django the permissions are not created until after
all the migrations are finished. So the resultant migration works fine
on my development box, but fails badly on new installs, including tests.
Looking at slashdot, I see questions like
https://stackoverflow.com/questions/42743825/how-to-create-groups-and-assign-permission-during-project-setup-in-django
which recommend setting up a post_migrate signal handler. Unfortunately,
signal handlers in Django are unordered, there is no guarantee our
handler will be called after the one that creates the permissions.
I could also have some sort of button in Django Admin that needs to be
manually pressed - would happen after permissions are created. Seems to
me though that doing significant changes to the database group table
from a HTTP request may not be ideal...
Any other suggestions? I am somewhat surprised that this situation
doesn't seem to have any good answers.
Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From miked at dewhirst.com.au Thu Sep 7 00:27:41 2017
From: miked at dewhirst.com.au (Mike Dewhirst)
Date: Thu, 7 Sep 2017 14:27:41 +1000
Subject: [melbourne-pug] Django: Automatically creating default groups
and assigning default permissions
In-Reply-To: <0279685e3d84528f8d960127d9b08ff0@linuxpenguins.xyz>
References: <0279685e3d84528f8d960127d9b08ff0@linuxpenguins.xyz>
Message-ID:
On 6/09/2017 3:43 PM, Brian May wrote:
>
> Hello,
>
> Just wondering how to create groups automatically in Django and
> automatically assign permissions?
>
> Sounds easy. I have created a database migration to do just this.
>
> The problem is under Django the permissions are not created until
> after all the migrations are finished. So the resultant migration
> works fine on my development box, but fails badly on new installs,
> including tests.
>
Can you separate the process into separate migrations? Each can have a
dependency on the one prior.
> Looking at slashdot, I see questions like
> https://stackoverflow.com/questions/42743825/how-to-create-groups-and-assign-permission-during-project-setup-in-django?which
> recommend setting up a post_migrate signal handler. Unfortunately,
> signal handlers in Django are unordered, there is no guarantee our
> handler will be called after the one that creates the permissions.
>
> I could also have some sort of button in Django Admin that needs to be
> manually pressed - would happen after permissions are created. Seems
> to me though that doing significant changes to the database group
> table from a HTTP request may not be ideal...
>
> Any other suggestions? I am somewhat surprised that this situation
> doesn't seem to have any good answers.
>
> Regards
>
>
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
From perdylan at gmail.com Mon Sep 4 01:04:22 2017
From: perdylan at gmail.com (Dylan Pereira)
Date: Mon, 4 Sep 2017 15:04:22 +1000
Subject: [melbourne-pug] How do I become a python developer?
Message-ID:
Hi,
I just had a general question. I have used python before and have loved it.
I would love to work as a python developer. I don't have any previous
experience except for writing a few python scripts in a previous role. What
would employers like to see when they hire a junior python dev. What does
it take to break into the industry?
Best Regards,
Dylan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From brian at linuxpenguins.xyz Thu Sep 7 01:40:13 2017
From: brian at linuxpenguins.xyz (Brian May)
Date: Thu, 07 Sep 2017 15:40:13 +1000
Subject: [melbourne-pug] Django: Automatically creating default groups
and assigning default permissions
In-Reply-To:
References: <0279685e3d84528f8d960127d9b08ff0@linuxpenguins.xyz>
Message-ID:
On 2017-09-07 14:27, Mike Dewhirst wrote:
> Can you separate the process into separate migrations? Each can have a dependency on the one prior.
Unfortunately, it isn't going to help. The fact remains that all
migrations have to complete before the post_migrate signal is called,
and this creates the permissions.
As much as I like Django, there are times like this where I very much
dislike the design decisions.
For now, I have gone for the admin approach. A button in the admin
interface to do the installation of the groups. We don't have many users
or groups, so it is fast. For now.
Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ben+python at benfinney.id.au Thu Sep 7 03:49:06 2017
From: ben+python at benfinney.id.au (Ben Finney)
Date: Thu, 07 Sep 2017 17:49:06 +1000
Subject: [melbourne-pug] How do I become a python developer?
References:
Message-ID: <85efrj9cel.fsf@benfinney.id.au>
Dylan Pereira writes:
> I just had a general question. I have used python before and have
> loved it. I would love to work as a python developer. I don't have any
> previous experience except for writing a few python scripts in a
> previous role. What would employers like to see when they hire a
> junior python dev. What does it take to break into the industry?
That depends very much on the employer and the time when you apply.
Some employers want to employ junior programmers who don't necessarily
need good Python skills, but must demonstrate an ability to solve
programming problems and work well in a business team.
An example is my current employer, WSP Digital. Get your up-to-date
r?sum? together, make a cover letter for why you are a good hire and can
learn more Python + Django + JavaScript, and send it to apply for a job
.
For other jobs, the employer might need more. Research specific
employers using lots of Python and who are hiring, see what specifically
they want in a new hire.
--
\ ?Technology is anything that wasn't around when you were born.? |
`\ ?Alan Kay |
_o__) |
Ben Finney
From william.leslie.ttg at gmail.com Thu Sep 7 20:24:39 2017
From: william.leslie.ttg at gmail.com (William ML Leslie)
Date: Fri, 8 Sep 2017 10:24:39 +1000
Subject: [melbourne-pug] How do I become a python developer?
In-Reply-To:
References:
Message-ID:
On 4 September 2017 at 15:04, Dylan Pereira wrote:
> Hi,
>
> I just had a general question. I have used python before and have loved it.
> I would love to work as a python developer. I don't have any previous
> experience except for writing a few python scripts in a previous role. What
> would employers like to see when they hire a junior python dev. What does it
> take to break into the industry?
>
I've got a bit of a list of things I expect people to know if they say
they are a professional developer, and all in all it's a few days of
study to become familliar enough with all of this set. You don't have
to know any of these inside out, but if they were bought up in an
interview you should be able to show some familliarity.
* Know how to use a DVCS. The one you are most likely to be asked
about is ``git``; and both github and bitbucket offer free git hosting
so try to get good at managing and describing your changes. Ideally
learn to manage feature branches, too. Version control is a matter of
good hygeine.
* Know how to use a debugger, either in your IDE or editor, or PDB in
a python terminal. You won't often need to use one (as writing tests
and printing stuff is usually so much quicker), but it will mean a lot
for your sanity if debugger commands are not something you have to
learn while frantically trying to figure out what went wrong.
* Oh yes. Tests! Know how to write a test, and run it using the test
runner. Do not get into the habit of running the test file directly,
it teaches you bad import hygeine. If you're on a posix system, Ctrl-R
in bash is a lifesaver for finding your last test command, modifying
it, and running again. Mine often look like ``pytest
foo/bar/test/test_baz.py`` and pytest can figure out from the
``pytest.ini`` in the current directory where the package root is.
With unittest, use package names, like ``python -m unittest
foo.bar.test.test_baz``.
* Know at least one web framework. Even if you're not doing web stuff,
it's really handy to be able to go from "these two systems need to
talk" to working communication in a few minutes. And also requests.
For bonus points, lxml.html or BeautifulSoup if you must.
* Be familliar enough with some database library that you can spin up
a database for trivial tasks. For small stuff, I tend to use
sqlalchemy.core on top of sqlite3. Be able to declare a schema,
create a database, insert rows, query for them. Some Pandas and
postgres knowledge tends to come in handy too.
* For bonus points, be able to build python packages. Know how to
write a ``setup.py`` and upload your package to pypi. It goes without
saying that you should understand how to lay out your source package -
understand how an import statement becomes a lookup in sys.modules and
a number of lookups on the filesystem, and then finally how paths are
mapped to module and package names. Here's a really nice article on
that subject: http://blog.habnab.it/blog/2013/07/21/python-packages-and-you/
I want to thank you for the question, too. When I got my first
programming job, the largest program I'd written was probably around
100 lines, to visualise something for a school project. Programming
was just something I did in the quiet hours. So I give the above list
not to discourage you from applying for work already, but rather that
these are the things an employer will most appreciate not having to
teach.
--
William Leslie
Notice:
Likely much of this email is, by the nature of copyright, covered
under copyright law. You absolutely MAY reproduce any part of it in
accordance with the copyright law of the nation you are reading this
in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without
prior contractual agreement.
From john.knight at tequity.com.au Thu Sep 7 20:58:50 2017
From: john.knight at tequity.com.au (John Knight)
Date: Fri, 8 Sep 2017 10:58:50 +1000
Subject: [melbourne-pug] How do I become a python developer?
In-Reply-To:
References:
Message-ID: <005601d3283d$a2785eb0$e7691c10$@tequity.com.au>
Nice helpful comments there - I would also suggest getting involved in local
MeetUps and offering your "services" pro-bono to solve some real life
problems and get projects under your belt
All the very best, John
John Knight?/?Tech Agent & Founder?
M: +61 402 234 813
Saltworth Pty Ltd?
P: +61 3 9670 9056?
Atlantis Tower, Suite 3201/288 Spencer Street. Melbourne, Victoria 3000
http://www.saltworth.com.au
?????????
-----Original Message-----
From: melbourne-pug
[mailto:melbourne-pug-bounces+john.knight=tequity.com.au at python.org] On
Behalf Of William ML Leslie
Sent: Friday, 8 September 2017 10:25 AM
To: Melbourne Python Users Group
Subject: Re: [melbourne-pug] How do I become a python developer?
On 4 September 2017 at 15:04, Dylan Pereira wrote:
> Hi,
>
> I just had a general question. I have used python before and have loved
it.
> I would love to work as a python developer. I don't have any previous
> experience except for writing a few python scripts in a previous role.
> What would employers like to see when they hire a junior python dev.
> What does it take to break into the industry?
>
I've got a bit of a list of things I expect people to know if they say they
are a professional developer, and all in all it's a few days of study to
become familliar enough with all of this set. You don't have to know any of
these inside out, but if they were bought up in an interview you should be
able to show some familliarity.
* Know how to use a DVCS. The one you are most likely to be asked about is
``git``; and both github and bitbucket offer free git hosting so try to get
good at managing and describing your changes. Ideally learn to manage
feature branches, too. Version control is a matter of good hygeine.
* Know how to use a debugger, either in your IDE or editor, or PDB in a
python terminal. You won't often need to use one (as writing tests and
printing stuff is usually so much quicker), but it will mean a lot for your
sanity if debugger commands are not something you have to learn while
frantically trying to figure out what went wrong.
* Oh yes. Tests! Know how to write a test, and run it using the test runner.
Do not get into the habit of running the test file directly, it teaches you
bad import hygeine. If you're on a posix system, Ctrl-R in bash is a
lifesaver for finding your last test command, modifying it, and running
again. Mine often look like ``pytest foo/bar/test/test_baz.py`` and pytest
can figure out from the ``pytest.ini`` in the current directory where the
package root is.
With unittest, use package names, like ``python -m unittest
foo.bar.test.test_baz``.
* Know at least one web framework. Even if you're not doing web stuff, it's
really handy to be able to go from "these two systems need to talk" to
working communication in a few minutes. And also requests.
For bonus points, lxml.html or BeautifulSoup if you must.
* Be familliar enough with some database library that you can spin up a
database for trivial tasks. For small stuff, I tend to use sqlalchemy.core
on top of sqlite3. Be able to declare a schema, create a database, insert
rows, query for them. Some Pandas and postgres knowledge tends to come in
handy too.
* For bonus points, be able to build python packages. Know how to write a
``setup.py`` and upload your package to pypi. It goes without saying that
you should understand how to lay out your source package - understand how an
import statement becomes a lookup in sys.modules and a number of lookups on
the filesystem, and then finally how paths are mapped to module and package
names. Here's a really nice article on that subject:
http://blog.habnab.it/blog/2013/07/21/python-packages-and-you/
I want to thank you for the question, too. When I got my first programming
job, the largest program I'd written was probably around
100 lines, to visualise something for a school project. Programming was just
something I did in the quiet hours. So I give the above list not to
discourage you from applying for work already, but rather that these are the
things an employer will most appreciate not having to teach.
--
William Leslie
Notice:
Likely much of this email is, by the nature of copyright, covered under
copyright law. You absolutely MAY reproduce any part of it in accordance
with the copyright law of the nation you are reading this in. Any attempt
to DENY YOU THOSE RIGHTS would be illegal without prior contractual
agreement.
_______________________________________________
melbourne-pug mailing list
melbourne-pug at python.org
https://mail.python.org/mailman/listinfo/melbourne-pug
From paul at metrak.com Thu Sep 7 22:00:57 2017
From: paul at metrak.com (paul sorenson)
Date: Thu, 7 Sep 2017 19:00:57 -0700
Subject: [melbourne-pug] How do I become a python developer?
In-Reply-To:
References:
Message-ID:
There is no one size fits all way. Every employer will have certain
skills they value.
There are plenty of online courses and tutorials - the more python you
do, the better you will be. Get involved in some python open source
projects and start fixing bugs.
good luck
On 9/3/2017 10:04 PM, Dylan Pereira wrote:
> Hi,
>
> I just had a general question. I have used python before and have
> loved it. I would love to work as a python developer. I don't have any
> previous experience except for writing a few python scripts in a
> previous role. What would employers like to see when they hire a
> junior python dev. What does it take to break into the industry?
>
> Best Regards,
> Dylan
>
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jason.robert.thomas.123 at gmail.com Fri Sep 8 19:56:48 2017
From: jason.robert.thomas.123 at gmail.com (jason thomas)
Date: Sat, 9 Sep 2017 09:56:48 +1000
Subject: [melbourne-pug] melbourne-pug Digest, Vol 135, Issue 4
In-Reply-To:
References:
Message-ID:
Hi,
I got into programming when I was a journalist, and have since left
journalism to be a dev. My first programming role was at a startup that I
learned about in this email thread (so you're in the right place) and
nowdays I do a c#.net job ... So I've been where you are now.
The thing that has gotten my face out there is having a public GitHub
profile. If you put your work there then it becomes a catalogue of what
you've done and employers see this as evidence of being keen.
The second thing I'd say is Python is a great language but it can only
teach you so much. To be a pro programmer, you need to not just be good at
one language. One of the most beneficial things I did after I was
comfortable with Python was learn c++, because it has a lot of features and
pitfalls that python doesn't have. Learning one will teach you about the
other.
It's been really good for me to read articles when I can, not necessarily
about Python, but just general programming concepts. As I've learned I've
applied those principles in my profiles on GitHub, and my projects today
are better as a result... And believe me my first ones were shockers, but
that's ok.
Other than that, I'd second what others have already said.
So that's how I did it. I applied for many, many jobs and was rejected many
times. So a combination of being lucky, being determined to learn, and
being really persistent with applying for jobs every week got me there.
Hope that helps,
On Saturday, 9 September 2017, wrote:
> Send melbourne-pug mailing list submissions to
> melbourne-pug at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.python.org/mailman/listinfo/melbourne-pug
> or, via email, send a message with subject or body 'help' to
> melbourne-pug-request at python.org
>
> You can reach the person managing the list at
> melbourne-pug-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of melbourne-pug digest..."
>
>
> Today's Topics:
>
> 1. Re: How do I become a python developer? (William ML Leslie)
> 2. Re: How do I become a python developer? (John Knight)
> 3. Re: How do I become a python developer? (paul sorenson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 8 Sep 2017 10:24:39 +1000
> From: William ML Leslie >
> To: Melbourne Python Users Group >
> Subject: Re: [melbourne-pug] How do I become a python developer?
> Message-ID:
> <
> CAHgd1hHdA9k1sOdJS4aG-yaiMrNmNhN1edkn6CJ1PFKsx55eQg at mail.gmail.com
> >
> Content-Type: text/plain; charset="UTF-8"
>
> On 4 September 2017 at 15:04, Dylan Pereira > wrote:
> > Hi,
> >
> > I just had a general question. I have used python before and have loved
> it.
> > I would love to work as a python developer. I don't have any previous
> > experience except for writing a few python scripts in a previous role.
> What
> > would employers like to see when they hire a junior python dev. What
> does it
> > take to break into the industry?
> >
>
> I've got a bit of a list of things I expect people to know if they say
> they are a professional developer, and all in all it's a few days of
> study to become familliar enough with all of this set. You don't have
> to know any of these inside out, but if they were bought up in an
> interview you should be able to show some familliarity.
>
> * Know how to use a DVCS. The one you are most likely to be asked
> about is ``git``; and both github and bitbucket offer free git hosting
> so try to get good at managing and describing your changes. Ideally
> learn to manage feature branches, too. Version control is a matter of
> good hygeine.
>
> * Know how to use a debugger, either in your IDE or editor, or PDB in
> a python terminal. You won't often need to use one (as writing tests
> and printing stuff is usually so much quicker), but it will mean a lot
> for your sanity if debugger commands are not something you have to
> learn while frantically trying to figure out what went wrong.
>
> * Oh yes. Tests! Know how to write a test, and run it using the test
> runner. Do not get into the habit of running the test file directly,
> it teaches you bad import hygeine. If you're on a posix system, Ctrl-R
> in bash is a lifesaver for finding your last test command, modifying
> it, and running again. Mine often look like ``pytest
> foo/bar/test/test_baz.py`` and pytest can figure out from the
> ``pytest.ini`` in the current directory where the package root is.
> With unittest, use package names, like ``python -m unittest
> foo.bar.test.test_baz``.
>
> * Know at least one web framework. Even if you're not doing web stuff,
> it's really handy to be able to go from "these two systems need to
> talk" to working communication in a few minutes. And also requests.
> For bonus points, lxml.html or BeautifulSoup if you must.
>
> * Be familliar enough with some database library that you can spin up
> a database for trivial tasks. For small stuff, I tend to use
> sqlalchemy.core on top of sqlite3. Be able to declare a schema,
> create a database, insert rows, query for them. Some Pandas and
> postgres knowledge tends to come in handy too.
>
> * For bonus points, be able to build python packages. Know how to
> write a ``setup.py`` and upload your package to pypi. It goes without
> saying that you should understand how to lay out your source package -
> understand how an import statement becomes a lookup in sys.modules and
> a number of lookups on the filesystem, and then finally how paths are
> mapped to module and package names. Here's a really nice article on
> that subject: http://blog.habnab.it/blog/2013/07/21/python-packages-
> and-you/
>
> I want to thank you for the question, too. When I got my first
> programming job, the largest program I'd written was probably around
> 100 lines, to visualise something for a school project. Programming
> was just something I did in the quiet hours. So I give the above list
> not to discourage you from applying for work already, but rather that
> these are the things an employer will most appreciate not having to
> teach.
>
> --
> William Leslie
>
> Notice:
> Likely much of this email is, by the nature of copyright, covered
> under copyright law. You absolutely MAY reproduce any part of it in
> accordance with the copyright law of the nation you are reading this
> in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without
> prior contractual agreement.
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 8 Sep 2017 10:58:50 +1000
> From: "John Knight" >
> To: "'Melbourne Python Users Group'" >
> Subject: Re: [melbourne-pug] How do I become a python developer?
> Message-ID: <005601d3283d$a2785eb0$e7691c10$@tequity.com.au>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Nice helpful comments there - I would also suggest getting involved in
> local
> MeetUps and offering your "services" pro-bono to solve some real life
> problems and get projects under your belt
>
> All the very best, John
>
> John Knight?/?Tech Agent & Founder?
> M: +61 402 234 813
> Saltworth Pty Ltd?
> P: +61 3 9670 9056?
> Atlantis Tower, Suite 3201/288 Spencer Street. Melbourne, Victoria 3000
> http://www.saltworth.com.au
> ?????????
>
> -----Original Message-----
> From: melbourne-pug
> [mailto:melbourne-pug-bounces+john.knight =
> tequity.com.au at python.org ] On
> Behalf Of William ML Leslie
> Sent: Friday, 8 September 2017 10:25 AM
> To: Melbourne Python Users Group >
> Subject: Re: [melbourne-pug] How do I become a python developer?
>
> On 4 September 2017 at 15:04, Dylan Pereira > wrote:
> > Hi,
> >
> > I just had a general question. I have used python before and have loved
> it.
> > I would love to work as a python developer. I don't have any previous
> > experience except for writing a few python scripts in a previous role.
> > What would employers like to see when they hire a junior python dev.
> > What does it take to break into the industry?
> >
>
> I've got a bit of a list of things I expect people to know if they say they
> are a professional developer, and all in all it's a few days of study to
> become familliar enough with all of this set. You don't have to know any
> of
> these inside out, but if they were bought up in an interview you should be
> able to show some familliarity.
>
> * Know how to use a DVCS. The one you are most likely to be asked about is
> ``git``; and both github and bitbucket offer free git hosting so try to get
> good at managing and describing your changes. Ideally learn to manage
> feature branches, too. Version control is a matter of good hygeine.
>
> * Know how to use a debugger, either in your IDE or editor, or PDB in a
> python terminal. You won't often need to use one (as writing tests and
> printing stuff is usually so much quicker), but it will mean a lot for your
> sanity if debugger commands are not something you have to learn while
> frantically trying to figure out what went wrong.
>
> * Oh yes. Tests! Know how to write a test, and run it using the test
> runner.
> Do not get into the habit of running the test file directly, it teaches you
> bad import hygeine. If you're on a posix system, Ctrl-R in bash is a
> lifesaver for finding your last test command, modifying it, and running
> again. Mine often look like ``pytest foo/bar/test/test_baz.py`` and pytest
> can figure out from the ``pytest.ini`` in the current directory where the
> package root is.
> With unittest, use package names, like ``python -m unittest
> foo.bar.test.test_baz``.
>
> * Know at least one web framework. Even if you're not doing web stuff, it's
> really handy to be able to go from "these two systems need to talk" to
> working communication in a few minutes. And also requests.
> For bonus points, lxml.html or BeautifulSoup if you must.
>
> * Be familliar enough with some database library that you can spin up a
> database for trivial tasks. For small stuff, I tend to use sqlalchemy.core
> on top of sqlite3. Be able to declare a schema, create a database, insert
> rows, query for them. Some Pandas and postgres knowledge tends to come in
> handy too.
>
> * For bonus points, be able to build python packages. Know how to write a
> ``setup.py`` and upload your package to pypi. It goes without saying that
> you should understand how to lay out your source package - understand how
> an
> import statement becomes a lookup in sys.modules and a number of lookups on
> the filesystem, and then finally how paths are mapped to module and package
> names. Here's a really nice article on that subject:
> http://blog.habnab.it/blog/2013/07/21/python-packages-and-you/
>
> I want to thank you for the question, too. When I got my first programming
> job, the largest program I'd written was probably around
> 100 lines, to visualise something for a school project. Programming was
> just
> something I did in the quiet hours. So I give the above list not to
> discourage you from applying for work already, but rather that these are
> the
> things an employer will most appreciate not having to teach.
>
> --
> William Leslie
>
> Notice:
> Likely much of this email is, by the nature of copyright, covered under
> copyright law. You absolutely MAY reproduce any part of it in accordance
> with the copyright law of the nation you are reading this in. Any attempt
> to DENY YOU THOSE RIGHTS would be illegal without prior contractual
> agreement.
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 7 Sep 2017 19:00:57 -0700
> From: paul sorenson >
> To: Melbourne Python Users Group >,
> Dylan
> Pereira >
> Subject: Re: [melbourne-pug] How do I become a python developer?
> Message-ID: >
> Content-Type: text/plain; charset="utf-8"
>
> There is no one size fits all way. Every employer will have certain
> skills they value.
>
> There are plenty of online courses and tutorials - the more python you
> do, the better you will be. Get involved in some python open source
> projects and start fixing bugs.
>
> good luck
>
>
> On 9/3/2017 10:04 PM, Dylan Pereira wrote:
> > Hi,
> >
> > I just had a general question. I have used python before and have
> > loved it. I would love to work as a python developer. I don't have any
> > previous experience except for writing a few python scripts in a
> > previous role. What would employers like to see when they hire a
> > junior python dev. What does it take to break into the industry?
> >
> > Best Regards,
> > Dylan
> >
> >
> > _______________________________________________
> > melbourne-pug mailing list
> > melbourne-pug at python.org
> > https://mail.python.org/mailman/listinfo/melbourne-pug
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: attachments/20170907/ab2b5943/attachment-0001.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> https://mail.python.org/mailman/listinfo/melbourne-pug
>
>
> ------------------------------
>
> End of melbourne-pug Digest, Vol 135, Issue 4
> *********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From walker.michael.luke at gmail.com Wed Sep 20 07:55:26 2017
From: walker.michael.luke at gmail.com (Michael Walker)
Date: Wed, 20 Sep 2017 21:55:26 +1000
Subject: [melbourne-pug] Fwd: BA Tech Consultant wanted on contract in
Melbourne for new new high performance computing (HPC) environment /
Supercomputer replacement
In-Reply-To:
References:
Message-ID:
This job opportunity might be of interest to some. I'm just the messenger,
the contact details are within.
Michael Walker
---------- Forwarded message ----------
Michael, I've just had this request through for a technical BA in Melbourne
on a contract with long-term potential to fulfill work packages including
but not limited to:
Hardware Replacement, New Operating system, Slurm Scheduling Software,
Lustre file system Software, New Portal, Launch and HPC & Data Centre
assessments of PUE or Thermal Management Assessment.
Obviously, the BA needs to be technically-minded but not technically strong
in HPC specifically. More importantly, this requires excellent
communication skills, requirements skills, technical brains and clear
documentation ability to translatie work package requirements to detailed
technical requirements and "abstract up" up low-level technical information
to a high-level general understanding.
A fab conduit undertaking:
- Creation and update of requirements traceability matrix against
solution architecture, design, test planning and hand-over to support.
- Providing technical analysis and preparing presentation of
recommendation to management.
- Continuously monitoring and analysing potential impacts to
requirements and technical scope.
- Develop and execute test plans; in conjunction with subject matter
experts. Conduct UAT sessions.
- Business process mapping of current state and desired state.
- Process mapping and documentation from HPC SME for End-user computing
(EUC) and web/portal deliverables.
- Develop Use Cases to be used by the HPC team to develop unit tests and
UAT scripts.
- Coordinate and/or facilitate information sessions and user training
for new HPC systems
I'm putting the word out now. If this sounds like you or someone you
know... please pass this on... email them/email me. EOI's to:
john.knight at saltworth.com.au
Full spec available to interested parties, please feel free to ask me any
questions ;)
Best, John[image: Saltworth Pty Ltd]
*John Knight* / Tech Agent & Founder
M: +61 402 234 813 <+61%20402%20234%20813>
*Saltworth Pty Ltd*
P: +61 3 9670 9056 <+61%203%209670%209056>
Atlantis Tower, Suite 3201/288 Spencer Street. Melbourne, Victoria 3000
http://www.saltworth.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ed at pythoncharmers.com Fri Sep 22 01:40:52 2017
From: ed at pythoncharmers.com (Ed Schofield)
Date: Fri, 22 Sep 2017 15:40:52 +1000
Subject: [melbourne-pug] Next Melbourne Python meeting - Monday 2 October
Message-ID:
Hi everyone!
We are looking forward to the October meeting of the Melbourne Python users group on Monday 2 October. We have some more interesting talks planned:
1. Renaldi Gondosubroto: Moving Ahead with Internet of Things Developments in Python (30 minutes)
Renaldi will discuss the past and present of IoT development with Python with examples from his own experience. One example is libraries that collect environmental data from remote devices via TCP connections. Next he will describe how IoT services such as AWS or ThingSpeak can connect and manage smart devices. Renaldi will also talk about the usefulness of this for consumer applications and thoughts on the future of Python for IoT.
2. Andrew Peel: All about locking: the why, what, and how
Andrew will describe what kinds of locking are needed to implement a thread-safe file system and how ScramFS implements locking.
When: 5.45pm for mingling; talks starting at 6pm
Where:
Outcome-Hub Co-Working Space
Suite 1, 121 Cardigan Street, Carlton
How to get there:
Walk 12 minutes north from Melbourne Central station.
Afterwards: general announcements and pizza. Then maybe drinks on Lygon Street. :-)
Sponsorship: many thanks to Outcome Hub for providing the venue and Python Charmers for ongoing Meetup sponsorship.
We hope to see you there! :-D
Best wishes,
Ed
--
Dr. Edward Schofield
Python Charmers
http://pythoncharmers.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From betsy at python.org Thu Sep 28 17:06:07 2017
From: betsy at python.org (Betsy Waliszewski)
Date: Thu, 28 Sep 2017 14:06:07 -0700
Subject: [melbourne-pug] PyCon 2018 CFP is Open!
Message-ID:
Hi,
Woohoo! The PyCon 2018 CFP is open!
Here is a link to all the information: https://us.pycon.org/2018/speaking/
- Tutorial proposals ? deadline is 24 November 2017 AoE.
- Talk, Poster, and Education Summit proposals ? deadline is 3 January
2018 AoE.
If you know of a company who might be interested in sponsoring, feel free
to share our prospectus: https://us.pycon.org/2018/sponsors/prospectus/. An
email intro to me would be wonderful.
Cheers,
Betsy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: