Jimmy Thrasibule writes:
> ...
> Is it possible, still keeping one unique ``setup.py`` file, to create
> 3 independent packages?
>
> * ``myproj.common``
> * ``myproj.subpackage1``
> * ``myproj.subpackage2``
>
> Also I'd like to specify that when installing ``myproj.subpackage1``,
> ``myproj.common
On Thursday, June 29, 2017 at 6:04:07 AM UTC-4, Test Banks wrote:
> Greetings Students,
>
> We do have Solution Manuals and Test Bank for FINANCIAL AND MANAGERIAL
> ACCOUNTING FOR MBAs 5TH EDITION BY EASTON at reasonable price. You can get
> above mentioned resources by sending email to pro.fas
Hi,
I've reorganized my Python project to be under a same name umbrella.
My project can now be seen as multiple subsystems than can depend on
each other. That means that every sub-package can now be distributed
alone so that only required dependencies can be installed.
The old structure:
/
Is it a reason why my messages appears always a long time (today 9
hours) on the list after I send it ?
Send at 19:14 UTC+2
Vincent
--
https://mail.python.org/mailman/listinfo/python-list
On Fri, Sep 29, 2017 at 12:14 PM, Bill wrote:
>
> I'll write for the possible benefit of any beginners who may be reading.
> I guess by definition, if one still has a "bug" it's because one doesn't
> quite understand what the code is doing. And I would say you should lose
> your license if you "f
Bill wrote:
Don't be afraid to write *really descriptive* output statements, and do
so even though you "don't need to".
Yeah, often when I'm writing something tricky I'll proactively
put in some code to print intermediate state to reassure myself
that things are on track. Being more verbose wit
Steve D'Aprano wrote:
(1) I know there's a bug in a specific chunk of code, but I'm having trouble
working out where. When everything else fails, if I perturb the code a bit
(reorder lines, calculate things in a different order, rename variables, etc)
it may change the nature of the bug enough fo
On 29/09/17 19:06, Steve D'Aprano wrote:
> In the standard library's contextlib.py module, there is a class for
> redirecting
> standard I/O streams, and two public functions. The code is short enough to
> reproduce here:
>
> # From Python 3.5
>
> class _RedirectStream:
> _stream = None
>
On Sat, Sep 30, 2017 at 5:14 AM, Bill wrote:
> I'll write for the possible benefit of any beginners who may be reading. I
> guess by definition, if one still has a "bug" it's because one doesn't quite
> understand what the code is doing. And I would say you should lose your
> license if you "fix
Chris Angelico wrote:
On Sat, Sep 30, 2017 at 2:42 AM, Steve D'Aprano
wrote:
Oh, and I'd like to make a (moderate) defense of a kind of "bug fixing by random
perturbation". Obviously making unrelated, arbitrary changes to code is bad.
But making non-arbitrary but not fully understood changes to
Steve D'Aprano wrote:
> In the standard library's contextlib.py module, there is a class for
> redirecting standard I/O streams, and two public functions. The code is
> short enough to reproduce here:
>
> # From Python 3.5
>
> class _RedirectStream:
> _stream = None
> def __init__(self,
On 09/29/2017 10:54 AM, Stefan Ram wrote:
In some languages, printing »'\n'«, the Unicode code point 10,
will have the effect of printing a line terminator, which might
mean that the output device actually receives »\r\n«.
The line terminator ostensibly depends on the operating
sy
On 29 September 2017 at 19:54, Stefan Ram wrote:
> In some languages, printing »'\n'«, the Unicode code point 10,
> will have the effect of printing a line terminator, which might
> mean that the output device actually receives »\r\n«.
>
> The line terminator ostensibly depends on the oper
On Sat, Sep 30, 2017 at 3:54 AM, Stefan Ram wrote:
> In some languages, printing »'\n'«, the Unicode code point 10,
> will have the effect of printing a line terminator, which might
> mean that the output device actually receives »\r\n«.
>
> The line terminator ostensibly depends on the op
On 29/09/17 19:54, Stefan Ram wrote:
> In some languages, printing »'\n'«, the Unicode code point 10,
> will have the effect of printing a line terminator, which might
> mean that the output device actually receives »\r\n«.
>
> The line terminator ostensibly depends on the operating
> sys
On Sat, Sep 30, 2017 at 3:46 AM, Steve D'Aprano
wrote:
> On Fri, 29 Sep 2017 03:01 pm, Chris Angelico wrote:
>
>> On Fri, Sep 29, 2017 at 2:38 PM, Steve D'Aprano
>> wrote:
>>> On Thu, 28 Sep 2017 03:56 pm, Bill wrote:
>>>
I worked in maintenance programming. You got the hand you were dealt!
On Fri, 29 Sep 2017 03:01 pm, Chris Angelico wrote:
> On Fri, Sep 29, 2017 at 2:38 PM, Steve D'Aprano
> wrote:
>> On Thu, 28 Sep 2017 03:56 pm, Bill wrote:
>>
>>> I worked in maintenance programming. You got the hand you were dealt!
>>> And you weren't allowed to "improve" the code unless the cu
On Sat, Sep 30, 2017 at 2:42 AM, Steve D'Aprano
wrote:
> Oh, and I'd like to make a (moderate) defense of a kind of "bug fixing by
> random
> perturbation". Obviously making unrelated, arbitrary changes to code is bad.
> But making non-arbitrary but not fully understood changes to relevant code
>
In the standard library's contextlib.py module, there is a class for redirecting
standard I/O streams, and two public functions. The code is short enough to
reproduce here:
# From Python 3.5
class _RedirectStream:
_stream = None
def __init__(self, new_target):
self._new_target = n
Stefan Ram wrote:
The customer pays for the solution. The software
manufacturer does the refactoring for it's own sake,
because when it's a longer running project, the
refactorings will pay for themself.
The customer owns the source code (at least where I was). YMMV
--
https://ma
On Fri, 29 Sep 2017 08:34 pm, D'Arcy Cain wrote:
> On 09/29/2017 03:15 AM, Steve D'Aprano wrote:
>> "Carefully-designed experiments" -- yeah, that is so totally how the coders
>> I've worked with operate *wink*
>>
>> I think that's an awfully optimistic description of how the average
>> programme
On Fri, 29 Sep 2017 07:11 pm, Wolfgang Maier wrote:
> On 29.09.2017 11:05, Wolfgang Maier wrote:
>> On 29.09.2017 07:25, Steve D'Aprano wrote:
>>> I'm pretty sure this is a bug.
>>>
>>
>> Yes, it is a bug, but a known one: https://bugs.python.org/issue20491
>>
>> The fix got backported even to 3
Le 29/09/17 à 08:58, Frank Millman a écrit :
"Steve D'Aprano" wrote in message
news:59cde998$0$14935$b1db1813$d948b...@news.astraweb.com...
On Fri, 29 Sep 2017 03:55 pm, Terry Reedy wrote:
Expected result:
Lorum ipsum dolor sit amet, consectetur adipiscing elit
ZZZ ZZZ sed do euismod tempo
On Sat, Sep 30, 2017 at 12:45 AM, Stefan Ram wrote:
> Chris Angelico writes:
>>If the behaviour remains *exactly* the same, then it's a code
>>improvement (aka a refactoring), not a bug fix.
>
> Usually, one cannot observe whether behavior stays the same,
> because a program does not map to b
On 9/29/2017 2:35 AM, Steve D'Aprano wrote:
On Fri, 29 Sep 2017 03:55 pm, Terry Reedy wrote:
Expected result:
Lorum ipsum dolor sit amet, consectetur adipiscing elit
ZZZ ZZZ sed do euismod tempor incididunt ut labore et
dolore magna aliqua.
On Windows 10, I get this on 2.7, 3.5, 3.6, 3.7.
On Fri, Sep 29, 2017 at 10:52 AM, justin walters wrote:
>
> I got through writing all of the above without realizing that you meant you
> wanted to build a
> desktop application and not a web application. Though, I think the advice
> is still helpful.
>
>
Yes and no. Seriously thanks!
I am at fi
On Fri, Sep 29, 2017 at 2:57 AM, Leam Hall wrote:
> On 09/27/2017 10:33 PM, Stefan Ram wrote:
>
>Some areas of knowledge follow, a programmer should not be
>>ignorant in all of them:
>>
>
> ---
>
> Stefan, this is list AWESOME!
>
> I have started mapping skills I have to the list and ways
On Fri, Sep 29, 2017 at 8:34 PM, D'Arcy Cain wrote:
> On 09/29/2017 03:15 AM, Steve D'Aprano wrote:
>>
>> "Carefully-designed experiments" -- yeah, that is so totally how the
>> coders I've
>> worked with operate *wink*
>>
>> I think that's an awfully optimistic description of how the average
>> p
On 09/29/2017 03:15 AM, Steve D'Aprano wrote:
"Carefully-designed experiments" -- yeah, that is so totally how the coders I've
worked with operate *wink*
I think that's an awfully optimistic description of how the average programmer
works :-)
Better not hire average programmers then. I do "Ca
On 2017-09-28 14:14, Neil Cerutti wrote:
> On 2017-09-28, Dan Sommers wrote:
>> If I'm hiring myself out as a plumber, I should know how to unclog
>> drains;
>
> OT: I recommend hiring a drain specialist, *not* a plumber for
> this particular job. Asking a plumber to clear a drain would be
> kind
On 09/27/2017 10:33 PM, Stefan Ram wrote:
Some areas of knowledge follow, a programmer should not be
ignorant in all of them:
---
Stefan, this is list AWESOME!
I have started mapping skills I have to the list and ways to build
skills I don't have. Last night I started working on a pro
On Friday, September 29, 2017 at 6:46:31 AM UTC+1, Frank Millman wrote:
> "Steve D'Aprano" wrote
>
> I don't have Python 3.6 installed, can somebody check to see whether or not
> it
> shows the same (wrong) behaviour?
>
> [...]
>
> C:\Users\User>python
> Python 3.6.0 (v3.6.0:41df79263a11, Dec
On 29.09.2017 11:05, Wolfgang Maier wrote:
On 29.09.2017 07:25, Steve D'Aprano wrote:
I'm pretty sure this is a bug.
Yes, it is a bug, but a known one: https://bugs.python.org/issue20491
The fix got backported even to 3.5, but I guess it depends which minor
version you are running. I'm pret
On 29.09.2017 07:25, Steve D'Aprano wrote:
I don't have Python 3.6 installed, can somebody check to see whether or not it
shows the same (wrong) behaviour?
import textwrap
text = ('Lorum ipsum dolor sit amet, consectetur adipiscing'
' elit ZZZ\xa0ZZZ sed do euismod tempor incididunt'
On 2017-09-29 08:58, Frank Millman wrote:
>
> It confirms that the problem was there in 3.5, but is fixed in 3.6.
>
Same on Linux: 3.5 has the bug, 3.6 doesn't.
(Python 3.5 from Red Hat, 3.6 from Anaconda)
--
Thomas Jollans
--
https://mail.python.org/mailman/listinfo/python-list
Steve D'Aprano wrote:
(say). Reading error messages is a skill that must be learned, even in Python.
Let alone (say) gcc error messages, which are baroque to an extreme. The other
day I was getting an error like:
/tmp/ccchKJVU.o: In function `__static_initialization_and_destruction_0(int,
int)'
On Fri, 29 Sep 2017 03:28 pm, Gregory Ewing wrote:
> Chris Angelico wrote:
>> finding the bug is basically searching
>> through a problem space of all things that could potentially cause
>> this symptom. A novice could accidentally stumble onto the right
>> solution to a tricky bug, or an expert c
"Steve D'Aprano" wrote in message
news:59cde998$0$14935$b1db1813$d948b...@news.astraweb.com...
On Fri, 29 Sep 2017 03:55 pm, Terry Reedy wrote:
Expected result:
Lorum ipsum dolor sit amet, consectetur adipiscing elit
ZZZ ZZZ sed do euismod tempor incididunt ut labore et
dolore magna aliqua.
38 matches
Mail list logo
