On 2018-02-07, Rob Gaddi wrote:
> On 02/07/2018 03:17 PM, Grant Edwards wrote:
>
>> How do you work on a package that must remain installed and usable the
>> whole time you're working on it?
>>
>> IOW, only specific test apps or apps run in a specific directory
>> should get the "in-progress" foo
Roel Schroeven writes:
> dieter schreef op 7/02/2018 8:21:
> ...
>> Likely, there are many ways to execute tests for your package.
>
>> I am using "setuptools" for packaging (an extension
>> of Python's standard "disutils"). Its "setup.py" supports the "test"
>> command. This means, properly set u
On 02/07/2018 03:17 PM, Grant Edwards wrote:
On 2018-02-07, Rob Gaddi wrote:
When I'm working on a module, the trick is to write a setup.py (using
setuptools) from the very get-go. Before I write a single line of code,
I've got a setup.py and the directory framework.
Then you install the pac
On 2018-02-07, Rob Gaddi wrote:
> When I'm working on a module, the trick is to write a setup.py (using
> setuptools) from the very get-go. Before I write a single line of code,
> I've got a setup.py and the directory framework.
>
> Then you install the package using pip -e (or in practice --u
Rob Gaddi schreef op 7/02/2018 22:24:
On 02/07/2018 12:34 PM, Roel Schroeven wrote:
dieter schreef op 7/02/2018 8:21:
Likely, there are many ways to execute tests for your package.
I am using "setuptools" for packaging (an extension
of Python's standard "disutils"). Its "setup.py" supports the
On 02/07/2018 12:34 PM, Roel Schroeven wrote:
dieter schreef op 7/02/2018 8:21:
Likely, there are many ways to execute tests for your package.
I am using "setuptools" for packaging (an extension
of Python's standard "disutils"). Its "setup.py" supports the "test"
command. This means, properly
dieter schreef op 7/02/2018 8:21:
Likely, there are many ways to execute tests for your package.
I am using "setuptools" for packaging (an extension
of Python's standard "disutils"). Its "setup.py" supports the "test"
command. This means, properly set up, I can run tests
with "python setup.py
Roel Schroeven writes:
> I'm fairly comfortable writing Python code, but I only have experience
> writing scripts with perhaps a few supporting modules. Now I want to
> start writing a package, and I'm feeling a bit helpless: I'm not sure
> how to organize my work.
You may have a look at
"https:/
I'm fairly comfortable writing Python code, but I only have experience
writing scripts with perhaps a few supporting modules. Now I want to
start writing a package, and I'm feeling a bit helpless: I'm not sure
how to organize my work.
In my way of thinking, I would have a working tree for the
