On 8/2/20 5:38 PM, o1bigtenor wrote:
> On Sun, Aug 2, 2020 at 2:08 PM Dennis Lee Bieber
> wrote:
>> On Sat, 1 Aug 2020 19:24:41 -0500, o1bigtenor
>> declaimed the following:
>>
>>> It is very disappointing - - - -suggests that thinking outside the space of
>>> one year is somehow deprecated. Fru
On Sun, Aug 2, 2020 at 2:08 PM Dennis Lee Bieber wrote:
>
> On Sat, 1 Aug 2020 19:24:41 -0500, o1bigtenor
> declaimed the following:
>
> >
> >It is very disappointing - - - -suggests that thinking outside the space of
> >one year is somehow deprecated. Frustrated when what you do demands
> >that
On Sun, Aug 2, 2020 at 2:28 PM Richard Damon wrote:
>
> On 8/2/20 12:58 PM, Dennis Lee Bieber wrote:
> > Yet follows what most /print/ calendars contain (though some companies
> > put the last four months of the current year in a 4-up page, before doing
> > one month per page for the new yea
On 8/2/20 12:58 PM, Dennis Lee Bieber wrote:
> Yet follows what most /print/ calendars contain (though some companies
> put the last four months of the current year in a 4-up page, before doing
> one month per page for the new year). "Daily planner" journals also tend to
> cover just one year
Richard Damon wrote:
> I would likely just build the formatter to start by assuming 6 week
> months, and then near the end, after stacking the side by side months,
> see if it can be trimmed out (easier to remove at the end then add if
> needed)
If you like some itertools gymnastics: you can form
On 8/2/20 7:26 AM, o1bigtenor wrote:
> The differences become very relevant for formatting. A month that has
> 4 weeks takes a different amount of vertical space than a month that
> has 6 weeks.
The only month that has only 4 weeks would be Febuary, on non-lead
years, that starts on Sunday (or wha
On 2020-08-02 at 06:26:10 -0500,
o1bigtenor wrote:
> On Sat, Aug 1, 2020 at 11:33 PM dn via Python-list
> wrote:
> > The fact that some months have fewer, or more, weeks to include, is
> > largely irrelevant. The solution is a standard "merge" algorithm. (us
> > 'silver surfers' cut our teeth o
On Sat, Aug 1, 2020 at 11:33 PM dn via Python-list
wrote:
>
> On 02/08/2020 12:24, o1bigtenor wrote:
> > On Sat, Aug 1, 2020 at 6:29 PM dn via Python-list
> > wrote:
> >> On 01/08/2020 23:36, o1bigtenor wrote:
> >>> On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
> >>> mailto:python-list@python
On 02/08/2020 12:42, o1bigtenor wrote:
On Sat, Aug 1, 2020 at 7:24 PM o1bigtenor wrote:
On Sat, Aug 1, 2020 at 6:29 PM dn via Python-list
wrote:
On 01/08/2020 23:36, o1bigtenor wrote:
On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
mailto:python-list@python.org>> wrote:
On 31/07/2020
On 02/08/2020 12:24, o1bigtenor wrote:
On Sat, Aug 1, 2020 at 6:29 PM dn via Python-list
wrote:
On 01/08/2020 23:36, o1bigtenor wrote:
On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
mailto:python-list@python.org>> wrote:
On 31/07/2020 02:52, o1bigtenor wrote:
> I regularly work i
On Sat, Aug 1, 2020 at 7:24 PM o1bigtenor wrote:
>
> On Sat, Aug 1, 2020 at 6:29 PM dn via Python-list
> wrote:
> >
> > On 01/08/2020 23:36, o1bigtenor wrote:
> > > On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
> > > mailto:python-list@python.org>> wrote:
> > >
> > > On 31/07/2020 02:52,
On Sat, Aug 1, 2020 at 6:29 PM dn via Python-list
wrote:
>
> On 01/08/2020 23:36, o1bigtenor wrote:
> > On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
> > mailto:python-list@python.org>> wrote:
> >
> > On 31/07/2020 02:52, o1bigtenor wrote:
> > > I regularly work in planning through mu
On 01/08/2020 23:36, o1bigtenor wrote:
On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
mailto:python-list@python.org>> wrote:
On 31/07/2020 02:52, o1bigtenor wrote:
> I regularly work in planning through multiple years at once.
> This means that I like to have a lot of stuff ava
> On Aug 1, 2020, at 10:35 AM, o1bigtenor wrote:
>
> On Sat, Aug 1, 2020 at 9:29 AM o1bigtenor wrote:
>>
>>> On Sat, Aug 1, 2020 at 6:58 AM Peter Otten <__pete...@web.de> wrote:
>>>
>>> o1bigtenor wrote:
>>>
>>> import calendar
>>> print (calendar.calendar(2024,1,1,2,8))
>>>
I
On Sat, Aug 1, 2020 at 9:29 AM o1bigtenor wrote:
>
> On Sat, Aug 1, 2020 at 6:58 AM Peter Otten <__pete...@web.de> wrote:
> >
> > o1bigtenor wrote:
> >
> > import calendar
> > print (calendar.calendar(2024,1,1,2,8))
> >
> > > I would like to show something like 2024 through the end of 20
On Sat, Aug 1, 2020 at 6:58 AM Peter Otten <__pete...@web.de> wrote:
>
> o1bigtenor wrote:
>
> import calendar
> print (calendar.calendar(2024,1,1,2,8))
>
> > I would like to show something like 2024 through the end of 2028.
>
> print("\n".join(cd.calendar(year) for year in range(2024, 20
o1bigtenor wrote:
import calendar
print (calendar.calendar(2024,1,1,2,8))
> I would like to show something like 2024 through the end of 2028.
print("\n".join(cd.calendar(year) for year in range(2024, 2029)))
--
https://mail.python.org/mailman/listinfo/python-list
On Sat, Aug 1, 2020 at 1:29 AM dn via Python-list
wrote:
> On 31/07/2020 02:52, o1bigtenor wrote:
> > I regularly work in planning through multiple years at once.
> > This means that I like to have a lot of stuff available in a calendar
> > function.
> > Python seems to be locked when I need to d
On 31/07/2020 02:52, o1bigtenor wrote:
I regularly work in planning through multiple years at once.
This means that I like to have a lot of stuff available in a calendar
function.
Python seems to be locked when I need to display more than 1 year at a
time.
I don't see a way to display something l
Greetings
I regularly work in planning through multiple years at once.
This means that I like to have a lot of stuff available in a calendar
function.
Python seems to be locked when I need to display more than 1 year at a
time.
I don't see a way to display something like 3 years worth of calendar
20 matches
Mail list logo
