my team is
following good practices.
I think the most important 'good practice' is rigorous testing, with at
least the basics repeated with every commit.
I am aware of pep8 but does that have project structure examples also?
If you intend to use github, I would look at a few othe
following good practices. I am aware of pep8 but does that have project
structure examples also?
--
https://mail.python.org/mailman/listinfo/python-list
I'm working on a project ( https://github.com/NJDFan/register-maps
http://register-maps.readthedocs.io/en/latest/ ) and running into some
issues with overall project structure and documentation.
The project is a code generator that reads in a set of proprietary
format XML files and uses
Simon Forman wrote:
In order for "from pymlb import fetcher" no work you must make the
'./pymlb' directory into a "package" by adding a file called
__init__.py (it can be empty.)
Then make sure the "top" directory (i.e. '.' in your example) is in
the python PATH. There are a couple of ways to
On Thu, Oct 29, 2009 at 3:45 PM, Simon Forman wrote:
> In order for "from pymlb import fetcher" no work you must make the
s/no/to/
D'oh!
--
http://mail.python.org/mailman/listinfo/python-list
On Thu, Oct 29, 2009 at 2:42 PM, Wells wrote:
> So I have my project partitioned like so:
>
> ./setup.py
> ./pymlb/
> ./pymlb/fetcher.py
> ./demos
> ./demos/demo.py
>
> In demo.py I have:
>
> from pymlb import fetcher
>
> However, it fails b/c pymlb is up a folder. It's also NOT installed as
> a m
So I have my project partitioned like so:
./setup.py
./pymlb/
./pymlb/fetcher.py
./demos
./demos/demo.py
In demo.py I have:
from pymlb import fetcher
However, it fails b/c pymlb is up a folder. It's also NOT installed as
a module in my module directory because it's a development effort and
I do
>
> This is first time that I am building python application that is
> larger than a single module and I would like to do it right.
I want to just say I am in agreement with the OP. Basically, there are a lot
of factors to balance out and consider when starting a python application
for the first
In article <[EMAIL PROTECTED]>,
Rafe <[EMAIL PROTECTED]> wrote:
>
>...and I completely agree. I always use the standard import form
>unless absolutely necessary. However, I use 'as' to shorten the path
>to the last module. For example:
import app.foo.bar as bar
instance = bar.Class()
Wh
On Nov 30, 11:43 pm, "Filip Gruszczyński" <[EMAIL PROTECTED]> wrote:
> This is first time that I am building python application that is
> larger than a single module and I would like to do it right. I google
> it a bit, finding some stuff about not using src directory (which I
> have seen so many t
Aaron Watters wrote:
On Nov 30, 11:55 am, "Filip Gruszczyński" <[EMAIL PROTECTED]> wrote:
http://jcalderone.livejournal.com/39794.html
That's exactly what I have read before posting here ;-)
--
Filip Gruszczyński
I too would like to see a meatier discussion of best practices
for python packa
On Nov 30, 11:55 am, "Filip Gruszczyński" <[EMAIL PROTECTED]> wrote:
> >http://jcalderone.livejournal.com/39794.html
>
> That's exactly what I have read before posting here ;-)
>
> --
> Filip Gruszczyński
I too would like to see a meatier discussion of best practices
for python packagizing. I par
> http://jcalderone.livejournal.com/39794.html
That's exactly what I have read before posting here ;-)
--
Filip Gruszczyński
--
http://mail.python.org/mailman/listinfo/python-list
On Sun, 30 Nov 2008 17:43:46 +0100, Filip Gruszczyński <[EMAIL PROTECTED]>
wrote:
This is first time that I am building python application that is
larger than a single module and I would like to do it right. I google
it a bit, finding some stuff about not using src directory (which I
have seen s
This is first time that I am building python application that is
larger than a single module and I would like to do it right. I google
it a bit, finding some stuff about not using src directory (which I
have seen so many times, that I believed it be standard) and using
packages. Still, there are fe
George Sakkis <[EMAIL PROTECTED]> writes:
> '''
> The __init__.py files are required to make Python treat the
> directories as containing packages; this is done to prevent
> directories with a common name, such as "string", from
> unintentionally hiding valid modules that occur later on the module
On Oct 10, 9:26 pm, jay graves <[EMAIL PROTECTED]> wrote:
> On Oct 10, 7:17 pm, amit <[EMAIL PROTECTED]> wrote:
>
> > How do create my own modules and import them? Right now it works but
> > they all have to be in the same directory. For example,
>
> > project/
> > util/
> > config/
> > ...
On Oct 10, 7:17 pm, amit <[EMAIL PROTECTED]> wrote:
> How do create my own modules and import them? Right now it works but
> they all have to be in the same directory. For example,
>
> project/
> util/
> config/
> tests/
> start.py
>
You need an __init__.py file (it doesn't matter
Hi,
I recently wrote a fairly complex project in python. It works great
and it was completed fairly quickly thanks to python!
Anyways, I am in the process of cleaning the code/directory and I had
a simple question
How do create my own modules and import them? Right now it works but
they all
19 matches
Mail list logo
